Usacomp2k3 wrote:So yeah, any ideas/thoughts/comments?
bitvector wrote:Usacomp2k3 wrote:So yeah, any ideas/thoughts/comments?
As a baseline, have you tried running nice on the script process (or related processes -- whatever apache vessel is running the script if it's not forked cgi)? A priority of 19 would have it get out of the way of everything else in terms of CPU scheduling. Any I/O initiated or work done in another process (like your database) could still cause sluggishness, but making the original script nice 19 may allow it to get out of the way and throttle it enough to at least be tolerable.
just brew it! wrote:Sounds like maybe the script is ill-behaved when you throw a lot of files at it. Just because Linux is generally better-behaved than Windows doesn't mean you can't hose it pretty bad by doing stuff like chewing up all the virtual memory.
just brew it! wrote:That doesn't look all that bad; load average is still less than 2.0, CPU isn't maxed out, and memory looks OK as well. The system really shouldn't be choking.
Usacomp2k3 wrote:Would I have to do that manually? Also, that would just take affect on that spawned process, right? Not a permanent change.
bitvector wrote:(Linux also adds in processes blocked in uninterruptible sleep, so heavy I/O can make your load average go sky high)
just brew it! wrote:bitvector wrote:(Linux also adds in processes blocked in uninterruptible sleep, so heavy I/O can make your load average go sky high)
Ahh, I wasn't aware of that. I guess I can say I've learned my new thing for the day!
bitvector wrote:The fact that your system froze could point to any number of things (including hardware problems). Have you tried looking through syslog (and /var/log/messages on debian/ubuntu) to see if anything blew up?
Usacomp2k3 wrote:Yup, exact same thing on the screen today (in as best as I can tell):
Usacomp2k3 wrote:If I'm going to pull down my web server for testing, I guess I can do that. Just not right now. I'm gone for the weekend, so probably next week. So run memtest for some time, I can do that. The failures both happened during fairly heavy strain of the 250gb storage drive, as it was copying pictures from one directory to another and then resize each one twice. That was also the hard drive that was in the computer when the other one died.
If I were to do some sort of hard drive test, what would you recommend? I believe it's a WD drive, so I guess I could just use the manufacturers test.
Users browsing this forum: Exabot [Bot] and 5 guests