quote: Oh, and there's this thing called planning for the future. Graphics companies don't have to do that as they just have to put more transistors in a smaller space, and voila, you got a bettter GPU!
quote: Only problem is that ATi and nVidia's product cycles change once every 6 months compared to Intel and AMD's cycle of 1-2 years.
quote: > "companies don't have to do that as they just have to put more transistors in a smaller space, and voila, you got a bettter GPU! "
...And how is that any different than on a CPU? "
quote: most desktop applications will never be able to use dozens of cores at once. So long-term, single-threaded performance sitll needs to improve
quote: Advances in languages, compilers, and tools open the possibility of significantly improving software. For example, Singularity uses type-safe languages and an abstract instruction set to enable what we call Software Isolated Processes (SIPs). SIPs provide the strong isolation guarantees of OS processes (isolated object space, separate GCs, separate runtimes) without the overhead of hardware-enforced protection domains. In the current Singularity prototype SIPs are extremely cheap; they run in ring 0 in the kernel’s address space.
quote: Singularity achieves good performance by reinventing the environment in which code executes. In existing systems, safe code is an exotic newcomer who lives in a huge, luxurious home in an elegant, gated community with its own collection of services. Singularity, in contrast, has architected a single world in which everyone can be safe, with performance comparable to the unsafe world of existing systems.
quote: A key starting point is Singularity processes, which start empty and add features only as required. Modern language runtimes come with huge libraries and expressive, dynamic language features such as reflection. This richness comes at a price. Features such as code access security or reflection incur massive overhead, even when never used.
quote: A Singularity application specifies which libraries it needs, and the Bartok compiler brings together the code and eliminates unneeded functionality through a process called "tree shaking," which deletes unused classes, methods, and even fields. As a result, a simple C# "Hello World" process in Singularity requires less memory than the equivalent C/C++ program running on most UNIX or Windows® systems. Moreover, Bartok translates from Microsoft® intermediate language (MSIL) into highly optimized x86 code. It performs interprocedural optimization to eliminate redundant run-time safety tests, reducing the cost of language safety.
quote: Aggressive interprocedural optimization is possible because Singularity processes are closed—they do not permit code loading after the process starts executing. This is a dramatic change, since dynamic code loading is a popular, but problematic, mechanism for loading plug-ins. Giving plug-ins access to a program's internals presents serious security and reliability problems [snip]... Dynamic loading frustrates program analysis in compilers or defect-detection tools, which can't see all code that might execute. To be safe, the analysis must be conservative, which precludes many optimizations and dulls the accuracy of defect detection.
quote: As for Mitosis, remember that its still very far down the horizon, as it requires hardware support that isn't in existence yet
quote: Furthermore, the amount of parallelism that can be extracted via Mitosis is rather limited. Diminishing returns sets in hard on anything over four cores
quote: From the same way one knows about the performance of any processor before it's built-- software simulation
quote: at 8 cores, the results are less impressive---about a 3.5X speedup