Page 1 of 1

Laptop makes good webserver?

Posted: Wed Feb 18, 2004 11:30 am
by liljester
I have a script that creates 10,000 randomly generated records. lots of looping and checking things before the insert... once they are created, then they are all updated.

so thats a lil over 20,000 queries.

and here are the results of the same script ran on different systems.

Dell PowerEdge (win2003 server)
Dual Xeon 3.06Ghz, 2Gb ddr2100 RAM, RAID 5
"created 10,000 sectors in 7.6855938434 seconds."
------------------------

No brand server (UNIX, FreeBSD)
P3 - 1266mhz, 256MB PC133, ATA133
"created 10,000 sectors in 8.17489695549 seconds."
------------------------

(this one broke my heart, I like AMD)
No Brand server (Win2000 server)
Athlon XP 1800+, 256MB DDR2100, ATA133
"created 10,000 sectors in 24.0805621147 seconds."
------------------------

Dell Inspiron 600M Laptop (WinXP Pro)
Pentium M 1.7GHz, 512MB DDR2100, ATA100
"created 10,000 sectors in 4.5380580425262 seconds."


I used the same script on each test. the versions of php and mysql where the same on all except the Dell PowerEdge Server (it had older version). All systems where dedicated webservers, with no other crap running on them.

anyone have any ideas/comments?

Posted: Wed Feb 18, 2004 4:48 pm
by Straterra
The problem, I think, is the older software. Update the software on the first machine and try it.

Posted: Wed Feb 18, 2004 4:49 pm
by Straterra
Also, look at this post I have made. Next time, post in the correct place.

Posted: Sat Feb 21, 2004 9:58 am
by tylerdurden
Can you post the exact code? I'd like to test this on my machine. (Apple G5)

Posted: Fri Feb 27, 2004 9:22 am
by liljester
id rather not =) its for a project im working on. it creates a 100x100 (10,000) grid and then reorders them into quadrants and then further into sectors...

basically it creates them (10000 inserts) then updates thier numbers (10000 updates) and a few other queries for fun.

on an update, we fixed the AMD server, it turns out it was performing so badly because of a bad bios setting (CAS Latencey) didnt match its memory. it runs around 7 secs now =)