With 1GHz in 2000 and 3GHz in 2002 10GHz CPUs were expected in 2005. Today, we should run much faster CPUs but:
We're not going to have faster processors. Instead, making software run faster in the future will mean using parallel-programming techniques. This will be a huge shift.
As multicore grows exponentially, software becomes exponentially CPU-bound, and efficiency matters exponentially:
Initialization & Maintenance Scripts
Config Backup Alert Monitoring Healing Async. Jobs
Connection Rewrites Filter Custom Errors Caching
Protocol DNS NTP HTTP SMTP POP3 LDAP
Servlet (edit & play) Scripts
Ø-conf. virtualized Code Compute Storage Network
G-WAN runs C, C# or Java with less CPU and less RAM while handling more requests than other servers. Other languages (Go, PHP, Python, Ruby, JS...) benefit from G-WAN's multicore architecture.
Use /usr/lib's thousands of libraries without writing complex interfaces: #pragma link "sqlite3"
Plug C/C++ libraries to support more protocols
G-WAN powers the mathematically-proven as secure, massively-scalable Global-WAN Cloud able to protect today's critical infrastructure and tomorrow's Internet of Things (IoT) with post-quantum security (PQE).
And, with raising energy costs, this increasingly large performance-gap paid by end-users will force all to migrate to the Cloud:
Why we didn't have 10GHz in 2005? CPU performance growth as we have known it hit a wall in 2003. Most people have only recently started to notice. Concurrency is the next major revolution in how we write software.