Quote:
Originally posted by XP
I'm the script owner, I'm also server guru ;)
boneprone has a p4 2.4ghz cpu (400 or 533mhz fsb I suppose) with no Hyperthreading. 2Gb ram and Freebsd 4.X
last pid: 26998; load averages: 1.12, 1.35, 1.83 up 7+10:32:19 01:09:37
849 processes: 3 running, 789 sleeping, 57 zombie
CPU states: 19.2% user, 0.0% nice, 26.8% system, 4.7% interrupt, 49.3% idle
Mem: 1022M Active, 394M Inact, 375M Wired, 59M Cache, 199M Buf, 161M Free
Swap: 2048M Total, 76M Used, 1972M Free, 3% Inuse
as I see, too many sleeping proccess that eat memory cause to use SWAP sometimes. When there is no script running, server runs ok. 1.0 to 2.0 loads are acceptable. But its at border. When a script runs from crontab, it begins to delay proccess and server is loaded with 3.0 to 7.0
I use same script on AMD Athlon XP 2.4 ghz, 512 ram server, which works fine without any load. Of course I only have one site hosted at this server, thats why.
I think Single Xeon 2.8ghz (800mhz fsb) with 1mb cache will resolve problem temporarily. But if he increases his hits like double them, a second xeon cpu may required.
Having a second server for thumbs also may help, but then they have to be syncronised frequently. Even thumbs hosted at a second server, a new cpu is required. He gets soo much clicks for UCJ ;)
|
Hey murat, those specs you just posted are rare.
Usually it looks more stressed than that 2:00 am Sunday Morning figure you posted.
The problem is yeah the server cripples when your script runs. No big deal really bro. It only runs for like 20 minutes 4 times a day.. I can deal with that..
The problem Im worried about is when the site isnt using cron tab im having some serious memory loads and lack idle of cpu avaible and swap running. I can see with my own eyes the links on my sites stalling when i click em and not shooting right to where the link is supposed to take em.
Its really affecting sites like boneprone.com which relys on this speed abilty of the surfer to click as much as possible.
My 200k site, is down at 50k after this weekend. And the click and prod according to the stats have never been lower..
Less clicks per surfer is clearly the problem. With less clicks on a tgp it can naturally have such a dramatic effect as going from 200k to 50k real fast. Now some people say that there may be a memory leak in a script that is casusing this.
Is this possible, if so how do we trace it.
Also 2 months ago we just said bahh lets put in 2 gigs of RAM from 1 gig and many of the load issues will be gone rather than looking deeper into the issue.
Now we have the 2 gigs of RAM and the same problem still exists.