I'm running Foreman on a box with 16GB RAM, an SSD and 8x3.30 GHz E3 CPUs
and am connected to the host NIC via loopback. However I've noticed that
when I do things "click on hosts etc" I routinely have to wait for a second
or more for things to appear. This situation exacerbates when foreman is
left "idle" (i.e. nothing has been done with it for hours or so) and I come
back to it.
Any ideas why it's so "laggy" and what I can do to speed it up? I'm quite
happy to trade off space (disk, RAM) for speed.
Thanks
Jassi
I don't know your configuration other than the hardware specs, but when you
run Foreman with Passenger with the default settings, you're actually using
apache httpd to launch Foreman and Passenger. There's always a noticeable
lag when Foreman is first accessed after an httpd restart because it has to
load the ruby code that Foreman and Passenger run, but after that it should
be relatively speedy. Another performance issue might be the database
you're using: the development database is just a sqlite3 database, which is
fine for small environments, but if you want to scale you'll have to use
the "production" environment and use postgresql or mysql.
ยทยทยท
On Monday, September 30, 2013 3:16:26 PM UTC-4, Jassi Singh wrote:
>
> I'm running Foreman on a box with 16GB RAM, an SSD and 8x3.30 GHz E3 CPUs
> and am connected to the host NIC via loopback. However I've noticed that
> when I do things "click on hosts etc" I routinely have to wait for a second
> or more for things to appear. This situation exacerbates when foreman is
> left "idle" (i.e. nothing has been done with it for hours or so) and I come
> back to it.
>
> Any ideas why it's so "laggy" and what I can do to speed it up? I'm quite
> happy to trade off space (disk, RAM) for speed.
>
> Thanks
>
> Jassi
>
