PDA

View Full Version : v4 - it's so slow!!! (*inaccurate* -WGM)


BlueC
09-24-2007, 09:27 PM
Just installed v4 to have a little look at what's new.

First impression is that it's just so slow! I always thought v3 was slow, and was hoping v4 would be much faster as it's completely re-written, but if anything it's slower.

It seems to take about 3-5 seconds on average to load a page - that isn't really very good. (Note, this is on a fresh install with no tickets imported or anything).

How is everyone else finding it? I really expected it to fly on our server as everything else does!

Spec:
Dedicated server (RHEL4)
Dual Xeon 3.2GHz CPU
6GB RAM
PHP v5.2.4
Apache v2.0.52
MySQL 4.1.20

jstanden
09-25-2007, 10:06 PM
Hey there,

Whatever you're experiencing, it isn't a code issue or some inherit performance problem. Cerb4 is a very lean code-base and heavily utilizes advanced caching.

Does your browser cache happen to be disabled? If you're re-downloading the javascript libraries and CSS each page (several connections) it would definitely impact performance.

jstanden
09-25-2007, 10:08 PM
For comparison:

* Our "instant evaluations" machine has had 1000 light-use installations going concurrently and they're all quick enough for demo purposes.

* Our "4.0 beta" installations machine has our own helpdesk plus helpdesks for about 100 testers. Our page loads are near-instantaneous.

Even on the Cerb3 hosting machines we provide, there are 25-50 installations on some of those machines without negatively impacting peformance.

One helpdesk, especially a 4.0, is not going to be a problem unless something else is going on.

When I get some time I can help you troubleshoot, but my first suggestion is to make sure you aren't preventing your browser from caching the client side JS/CSS.

BlueC
09-25-2007, 11:08 PM
Hi Jeff, thanks for responding.

Sorry if it seemed I was slating v4, I wasn't intending to (I really rather like it!), more I wanted to know whether anyone else had experienced extreme slowness and to ask why it may be.

I didn't think it was a problem with the v4 code per se, but some kind of problem between v4 and my server setup or browser setup.

My browser cache isn't disabled (about:config --> browser.cache.disk.enable=true) - cerb3 loads fairly quick and other sites/applications on our server load very quickly.

Ahhh... you could have been barking up the right tree though! Maybe it's because "browser.cache.disk_cache_ssl" is set to false, and i always access cerberus through SSL. I'll have a try with non-ssl access, and also try setting that option to true.

jstanden
09-25-2007, 11:11 PM
Hi Jeff, thanks for responding.
Sorry if it seemed I was slating v4, I wasn't intending to (I really rather like it!), more I wanted to know whether anyone else had experienced extreme slowness and to ask why it may be.

No problem! I wasn't trying to be overly defensive either. ;)

Ahhh... you could have been barking up the right tree though! Maybe it's because "browser.cache.disk_cache_ssl" is set to false, and i always access cerberus through SSL. I'll have a try with non-ssl access, and also try setting that option to true.

Hopefully that's all it is! Let us know and I'll add it to the knowledgebase.

Thanks!

BlueC
09-25-2007, 11:21 PM
I haven't got v4 to hand right now (I removed it after a quick-test) but i'll have another look at it tomorrow and get back to you.

Meanwhile, I have some info on installing mailparse from source on linux that may be useful for the wiki... i'll start another thread somewhere.

jstanden
09-25-2007, 11:22 PM
Excellent, thanks!

chewtoy
03-14-2008, 10:38 PM
I realize this is an old thread, but if someone else starts thinking "cerb4 is slow", I'd note your latency. On my system, cerb4 is quite fast/instantaneous on all pages as long as I'm on the same LAN (latency in microseconds), but when I'm elsewhere and having latency of 80-100 milliseconds, it's actually quite slow to get enough of the page pieces back to draw a whole page. Not quite sure what to suggest doing about it, and I don't even suggest it's a problem. I'm just noting that latency has a more noticeable impact on time-to-draw for complicated cerb pages than for your typical web page.