Jason Salas' WebLog

On-air and online: making people laugh, making people think, pissing people off

Sponsors

ASP.NET sites that kick ass

Pals with blogs

Podcasts I listen to

So that's what RAM's used for...

I've been jamming on an app for the last 2 months, a big voter update process that we're only going to use once to keep voting totals in synch across multiple platforms.  The one thing that's bewildered me has been the painfully slow-ass performance. 

In tests on my staging server (a WinXP Pro box w/256MB of RAM), the process cycled through more than 100 candidates and updated a DataSet...and took about 19 seconds to do so.  Which totall had me stumped.  It was a somewhat large job, but nothing extraordinary, and not really that daunting for a processor.  It just ran slow.  I even rebuilt it using a SqlDataReader (I'm using a SqlDataAdapter now), and it still wouldn't fly fast enough/

I finally said “forget it” (but I didn't really say “forget“) and deployed the app to my production server, which sports a couple of gigabytes of RAM and multiple monster processors and the same process ran, without any modifications in about 2 seconds!

D-uh!

Comments

TrackBack said:

Lazycoder weblog » tight code and more RAM
# July 20, 2004 7:09 PM

stefan demetz said:

probably the ASPNET process was paging on your pc with little RAM
# July 21, 2004 4:06 AM

Jason Salas said:

geez...256MB ain't what it used to be...
# July 21, 2004 4:43 AM

zane coghlan said:

u missed the y of totally :P

# November 19, 2007 10:54 AM

Mr Houghten said:

meeeoooowwww!!!!!!

# November 27, 2008 9:17 AM

Mr Royal said:

this is a bit borin!! why do we need to do ICT man init like scribble back to dat shizzle xoxo

# November 27, 2008 9:45 AM
Leave a Comment

(required) 

(required) 

(optional)

(required)