Skip to main content

clovertown from INTEL

This is from from a recent site that i visited , heres a peek into whats intel is cooking for its costumer this 2006:

Clovertown, a four-core processor, will start shipping to computer manufacturers late this year and hit the market in early 2007. Clovertown will be made for dual-processor servers, which means that these servers will essentially be eight-processor servers (two processors x four cores each).

The company will also come out with a previously announced version called Tigerton around the same time for servers with four or more processors.

Core expansion will be a dominant theme for Intel over the next few years, said Chief Technology Officer Justin Rattner. By the end of the decade, chips with tens of cores will be possible, while in 10 years, it's theoretically possible that chips with hundreds of cores will come out, he added.

Rattner showed off a computer running two Clovertown processors

By working with one server application developer, Intel determined that it needed to make three small changes to the architecture of one of its future server chips. Before the changes, the application only ran well in simulations on chips with 16 cores. After that, performance began to decline, Rattner said.

After the changes, performance continued to climb. "We got it to scale well past 32" cores, he said.

Another pending change to chip design to accommodate problems that arise with core multiplication are Through Silicon Vias, or TSVs. With TSVs, processors and memory chips are stacked up and connected through tiny wires; the top of one chip wires directly into the bottom of another. Currently, chips connect through buses, long data paths that have become as crowded as rush-hour freeways in some computers.

Clovertown and Tigerton are members of a new chip architecture coming from Intel at the end of the year. A notebook chip called Merom and a desktop chip called Conroe coming out around the same time will be based on the same architecture. Intel will give the architecture a name at the Intel Developer Forum taking place in March.

Rattner indicated that Merom and Conroe will only be dual-core chips, as many analysts expect.

Comments

Popular posts from this blog

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python.

The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below:
Copy and paste the lines below :

"**/*.pyc":{"when":"$(basename).py"},"**/__pycache__":true

Get Started with MongoDB Stitch : The New Backend As Service Offering from MongoDB

Halfway of this year, the guys from MongoDB launch their new backend as service product called MongoDB Stitch. While the launch is just for the beta, the promise of the service is quite interesting. MongoDB has been around for long now and some development stacks have been based on its database product, the MongoDB-ExpressJS-Angular-NodeJS (MEAN) and the MongoDB-ExpressJS-React-NodeJS (MERN) stacks to name a few. These stacks, however, relies on backend technology such as ExpressJS and NodeJS. The idea of provisioning servers and developing the backend solution makes it daunting for small to medium scale applications. MongoDB Atlas, at least made life much easier by providing on cloud database solution, but there must be a simpler solution, right? A solution the would stitch the backend and frontend together ( see what I did there ?).
MongoDB Stitch lets developers focus on building applications rather than on managing data manipulation code, service integration, or backend infrastruct…

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and Windows Workflow Foundation(WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time.

Why reinvent the wheel? So I started querying the internet for a better solution. I stumbled upon Stateless