Joel Pobar speaks, consults, and teaches .NET technologies: CLR; programming languages; threading; platforms and more. A former Microsoft Program Manager, since leaving Microsoft he has been tinkering with v.next software: machine learning, natural language processing, programming languages and more.
I was reminiscing about the good 'ol days tinkering with computers: Commodore 64s, GWBASIC, Turbo Pascal 5.0, DOOM and the Autoexect.bat config.sys hacking required to get it running on underprivileged 486s, Amiga 500s, broken Linux 1.0 kernel compiles, EGA video cards and more Sierra ...
On to part two in the series of Most Excellent Software Adventures. In this episode, we talk about scalability in the massive sense - à la Google style. Thousands of commodity machines, connected and waiting for your algorithm and data inputs, and the APIs that drive them.
If we believe that dual/quad/octa/n-tuple cores + cache scaling + internals advancements is going to be the default way that processors are expected to scale, we must adjust the software appropriately to scale with it. When you start to think about how to solve the problem, an interest...
Dec. 7, 2007 05:15 AM Reads: 7,945
SUBSCRIBE TO OUR RSS FEEDS & GET YOUR SYS-CON NEWS LIVE!
Click to Add our RSS Feeds to the Service of Your Choice:
Joel Pobar speaks, consults, and teaches .NET technologies: CLR; programming languages; threading; platforms and more. A former Microsoft Program Manager, since leaving Microsoft he has been tinkering with v.next software: machine learning, natural language processing, programming languages and more. 
I was reminiscing about the good 'ol days tinkering with computers: Commodore 64s, GWBASIC, Turbo Pascal 5.0, DOOM and the Autoexect.bat config.sys hacking required to get it running on underprivileged 486s, Amiga 500s, broken Linux 1.0 kernel compiles, EGA video cards and more Sierra ...
On to part two in the series of Most Excellent Software Adventures. In this episode, we talk about scalability in the massive sense - à la Google style. Thousands of commodity machines, connected and waiting for your algorithm and data inputs, and the APIs that drive them.
If we believe that dual/quad/octa/n-tuple cores + cache scaling + internals advancements is going to be the default way that processors are expected to scale, we must adjust the software appropriately to scale with it. When you start to think about how to solve the problem, an interest...
