A Kick in the Pants

Duende

Duende

New member
Is it just me, or did CMON just get faster?

Pages were taking forever to load but recently I noticed a marked difference in load times, as well as Chern being logged in..

Was something tweaked? If so, GREAT! Faster is better!! (well, only in some cases....;) )


:D:D:D:D:D:D:D
 
H

hakoMike

Active member
CMON gets more traffic than the univsity web portal I administer, and I know how hard it is to improve performance of our stuff.

Well done. You have our respect.

(for the record, network has a lot to do with speed too. My work machine is much slower loading cmon pages than my home machine, despite being a faster machine overall.)
 
Chern Ann

Chern Ann

Only when they're green
Staff member
I only regret not doing this a year ago
mur.gif
. The lesson here in case anyone reading this has to deal with MySQL is, don\'t update the same table you\'re reading from on every page. The query cache is cleared every time the table is updated, there\'s a huge IO write overhead when writing to a large table that is better handled as a batch rather than per user.

Now data that is being updated is stored in a temporary table before being transferred to the main table in batches. The browse page reads a static cache that is updated every hour instead of the live image database. It looks and feels the same to an end user but is more than 10 times faster.
 
G

generulpoleaxe

New member
i don\'t have a clue what your on about.

it sounds technical.

it also sounds like you learned something from it.

i know this, things work faster now

and you rock:cool:
 
O

Ogrebane

Active member
Ahhh!!! Its all clear to me now. The answer is 42

Thanx Chern visit the freak bar Im sure you get to drink for free. If not put it on Finn or Dauber/Vikes account
 
H

hakoMike

Active member
Originally posted by Chern Ann
I only regret not doing this a year ago
mur.gif
. The lesson here in case anyone reading this has to deal with MySQL is, don\'t update the same table you\'re reading from on every page. The query cache is cleared every time the table is updated, there\'s a huge IO write overhead when writing to a large table that is better handled as a batch rather than per user.

Now data that is being updated is stored in a temporary table before being transferred to the main table in batches. The browse page reads a static cache that is updated every hour instead of the live image database. It looks and feels the same to an end user but is more than 10 times faster.
Click to expand...
Nice!
 
You must log in or register to reply here.
Back To Top
Top