Welcome to Geeklog, Anonymous Friday, May 10 2024 @ 11:25 pm EDT

Comments for performance tuning GL

performance tuning GL | 9 comments | Create New Account

The following comments are owned by whomever posted them. This site is not responsible for what they say.

performance tuning GL

Authored by: Dirk on Tuesday, November 26 2002 @ 12:23 am EST

If you have a lot of users, this may help.

And since you mentioned indexes: This script will add several indexes (including the one from the above-mentioned story) to Geeklog's tables which should speed things up a bit, we hope (this will also be part of the next Geeklog release).

bye, Dirk

performance tuning GL

Authored by: amckay on Tuesday, November 26 2002 @ 04:04 am EST

After just a few seconds that seems to be cutting at least a second off generation times on all pages!!!

thanks!
-Alan

performance tuning GL

Authored by: Anonymous (Anonymous User) on Saturday, May 31 2003 @ 06:39 am EDT

Hi,

the best thing for getting more performance and saving ressources is avoid
using the slow apache webserver.

there exists several fast and small webservers. at this point i can
recommend lightthttpd for personal sites and for professional services the
premium thttpd from sascha schumann.

lighthttpd: http://jan.kneschke.de/projects/lighttpd/

Here is a compare of both:
http://schumann.cx/gbit_deathmatch.txt

ATM i have running lighthttpd on several computers with vhosts. Before i
used apache 1.3.x (because apache 2 is still unstable with php) and i
recognized 20-40% of performance increasement with less use of memory
and cpu. (apache runs without output compression, lightthttpd runs with
output compression)

just a my 2 cents, maybe somebody finds this links useful.

regards,
kosch

performance tuning GL

Authored by: Anonymous (Anonymous User) on Saturday, May 31 2003 @ 03:59 pm EDT

Your results are flawed. A person can easily enable compression on Apache too using ini.zlib.output_compression or ob_gzhandler. If a site gets any significant traffic, compressed pages will cause the CPU usage to shoot way up and slow the server down to a crawl even on the one you recommend.

performance tuning GL

Authored by: Anonymous (Anonymous User) on Sunday, June 01 2003 @ 04:28 am EDT

Yes, as i said i tested apache+mod_php w/o compression and it is
significant slower and take more cpu/ram then it does with lighttpd _with_
optional compression enabled.

Ok, it has to be said that lighttpd uses fastcgi interface, and like Zeus it
does and it in this way anyway faster than using mod_php in apache.

It was just a hint from me. Its the same like using Tomcat from apache. if you
have enough ram/cpu you can use it... otherwise you would choose Resin or
Jetty...

Search

Resources

About

Getting started

Support

Development

Topics

User Functions

What's New

Articles last 4 weeks

Comments last 4 weeks

Pages last 4 weeks

Links last 4 weeks

Downloads last 4 weeks