Fastest PhpNuke Yet But Need More

perfect-games · Regular Joined: Oct 28, 2004 Posts: 81

hi guys well working on version 4 of my phpnuke distro so far i managed to get the queries down quite low and i have not even added cache yet
but php still showing on the high side what would you reccomened to lower the sql usage on my server
[ Script generation time: 0.361s (PHP: 70% - SQL: 30%) ] - [ SQL queries: 32 ] - [ Pages served in past 5 minutes : 21 ] - [ GZIP disabled ] - [ Debug off ]

thanks
steve

perfect-games · Regular Joined: Oct 28, 2004 Posts: 81

if i remove all the db files not needed like msaccess, odbc etc would this help imrove performance, is there anything else i can do to get loads of speed, as i want to speed this distro up before i add the hacks to it
thanks
steve

Raven · Posted: Sun Mar 06, 2005 1:29 am

Removing files has ZERO impact on nuke's performance Smile

perfect-games · Regular Joined: Oct 28, 2004 Posts: 81

i have rewrote most of the sql layer, but as you have experienced chache on nuke whats the best to go for as i want to include this in the distro,
i already have gt nextgt admin panel, meta in admin panel , trying to make this easier for everone to use
thanks
steve

perfect-games · Regular Joined: Oct 28, 2004 Posts: 81

whats the main parts of nuke i should look at for speed, i have removed all lang except english, it seems the biggest impact on nuke is the blocks without them its so low like close to 10 queries would cache sort this problem out, i was thinking if there is a good cache so when users install my ditro there wont be much work for them to do,
as jpcache you have to give the full url of the includes home/username/hhtp_public/includes is there an better way of doing this so it will work straight out of the box with out having the full url

djmaze · Posted: Tue Mar 08, 2005 4:20 pm

There are several ways to reduce SQL load by merging queries and other stuff.
The disadvantages could be slow queries or high memory usage.

The trick is to find the best solution for each individual module/file.
Biggest query eaters are is_admin() and is_user() as explained by steven111, someone i forgot name of and me on nukecops.com after a discussion about duplicate/re-occuring queries.

A good cache system also speeds up your system, but be carefull since it also eats more memory in PHP itself.

The best way to find out, is to list all queries each page calls.