Re:Intel: an expensive many-core future is ahead of us
by ntoshev on Wednesday July 02, 2008 @01:54PM
(#234342)
Multicore is nothing special if you are doing web apps. So I guess the trend towards multicore and the trend towards web apps will reinforce each other.
[ Parent
| on HN ]
Re:Intel: an expensive many-core future is ahead of us
by jrockway on Wednesday July 02, 2008 @04:31PM
(#234511)
Untrue.
Now that CPU time is really cheap, memory is expensive again. For example, I have a $30/month slicehost and only get 512M of RAM. Even though I have 4 cores on that box, my application uses too much memory per instance for me to be able to run 4 separate processes. So if I needed to scale, I would either need to buy more memory, or design my app better. Buying more memory works for 4 cores, but what about 128? Probably not.
Re:Intel: an expensive many-core future is ahead of us
by ntoshev on Thursday July 03, 2008 @04:34PM
(#235630)
Yeah, memory handling of Ruby is severely broken. Enterprise Ruby might help you.
If you use thread-based model for handling web requests (JVM or .NET application), you won't have this problem. I think even Python processes would share most of their memory.
Re:Intel: an expensive many-core future is ahead of us
by pchristensen on Wednesday July 02, 2008 @02:39PM
(#234403)
Yep, let the people writing the web servers, app servers, languages, and libraries deal with multicore. I'll happily run on those uber-optimized platforms.