'Free Mobile Phones,iPods to find out more offers click the link below'
Xpango
Thursday, January 11, 2007
Thursday, November 23, 2006
WHAT HAPPENED TO CLOCK SPEED
At the start of the PC industry, PC buyers used clock speed to gauge
performance because different PC processors were on par in efficiency.
Part of IBM's decision to use x86 processors for the original
IBM PC was to ensure multiple sources of compatible components.
In ensuring x86 compatibility, processor vendors developed processors
that were similar in their internal designs, or architectures. As a
result, clock speed became the distinguishing characteristic of the
PC processor.
The situation changed, however, in the middle and late 1980s as the
PC began to serve a greater variety of tasks and applications. More
than word processors, PCs became drawing tools, entertainment
appliances, and communication devices. They also began going outside
the office and into homes, on the road, and into the back office
where only mainframes and mini-computers used to reside. From
the increasingly varied uses and locales evolved a greater number
of user profiles, or usage models, with special requirements for PCs
to fulfill.
Accordingly, processor designs evolved, but not merely by scaling
the clock speed. In October 1985, for example, Intel introduced the
80386 processor, which doubled the amount of transistors in the
prior generation's 80286 processor and introduced 32-bit computing
to the PC. These advances were far more beneficial to PC performance
than the advance from the 80286's 12MHz to the 80386's
16MHz. Advances that took place in subsequent designs made the
processor's job easier by integrating small memory caches that
stored the data closer to the processor core. Designers also
improved efficiency by integrating other components, such as float-
External Publication of IDC Information and Data — Any IDC information that is to be used in advertising, press releases, or promotional materials
requires prior written approval from the appropriate IDC Vice President or Country Manager. A draft of the proposed document should accompany
any such request. IDC reserves the right to deny approval of external usage for any reason.
Is Megahertz Enough?
Printed on
recycled
materials
What does a proper measure of PC performance do? Why
shouldn't PC buyers use processor clock speed exclusively?
IDC believes that a proper measure of performance reflects how
much work a PC does in a given period of time. That requires
knowing how much time the PC worked and how efficiently it
worked. Clock speed alone is not a good measure of PC performance
because it does not account for performance efficiency.
Efficiency is determined by other factors.
Those factors include the processor architecture and how the
rest of the PC — the graphics controller, main memory, hard
drive, and so on — contributes to the work that gets done. Since
a PC has many components and simultaneous tasks, clock
speed only represents one facet of one component and is not
enough to measure the real performance of the entire system.
IDC OPINION
Accordingly, processor designs
evolved, but not merely by scaling the
clock speed.
– 3 – Is Megahertz Enough?
ing point units, and introduced more efficient techniques of data processing,
including adding more processing lines (pipelines) and processing
data and instructions to run the critical tasks first. Designers
also found ways to make processors work better in the context of the
entire system by introducing new instructions (e.g., MMX™ and
3DNow!™ Professional for multimedia) that were optimized for richer
data processing and by giving the processor a faster front-side bus
to the rest of the system.
Due to the different requirements of specific form factors and segments,
different processors from even the same vendor began to
deliver varied performance at the same clock rate. The issue
became more apparent when vendors like AMD moved to develop
their own architectures that, while still compatible with the x86
instruction set, took different approaches to maximize performance.
These approaches included changes that impacted both the processor
and the system (e.g., improved front-side buses).
performance because different PC processors were on par in efficiency.
Part of IBM's decision to use x86 processors for the original
IBM PC was to ensure multiple sources of compatible components.
In ensuring x86 compatibility, processor vendors developed processors
that were similar in their internal designs, or architectures. As a
result, clock speed became the distinguishing characteristic of the
PC processor.
The situation changed, however, in the middle and late 1980s as the
PC began to serve a greater variety of tasks and applications. More
than word processors, PCs became drawing tools, entertainment
appliances, and communication devices. They also began going outside
the office and into homes, on the road, and into the back office
where only mainframes and mini-computers used to reside. From
the increasingly varied uses and locales evolved a greater number
of user profiles, or usage models, with special requirements for PCs
to fulfill.
Accordingly, processor designs evolved, but not merely by scaling
the clock speed. In October 1985, for example, Intel introduced the
80386 processor, which doubled the amount of transistors in the
prior generation's 80286 processor and introduced 32-bit computing
to the PC. These advances were far more beneficial to PC performance
than the advance from the 80286's 12MHz to the 80386's
16MHz. Advances that took place in subsequent designs made the
processor's job easier by integrating small memory caches that
stored the data closer to the processor core. Designers also
improved efficiency by integrating other components, such as float-
External Publication of IDC Information and Data — Any IDC information that is to be used in advertising, press releases, or promotional materials
requires prior written approval from the appropriate IDC Vice President or Country Manager. A draft of the proposed document should accompany
any such request. IDC reserves the right to deny approval of external usage for any reason.
Is Megahertz Enough?
Printed on
recycled
materials
What does a proper measure of PC performance do? Why
shouldn't PC buyers use processor clock speed exclusively?
IDC believes that a proper measure of performance reflects how
much work a PC does in a given period of time. That requires
knowing how much time the PC worked and how efficiently it
worked. Clock speed alone is not a good measure of PC performance
because it does not account for performance efficiency.
Efficiency is determined by other factors.
Those factors include the processor architecture and how the
rest of the PC — the graphics controller, main memory, hard
drive, and so on — contributes to the work that gets done. Since
a PC has many components and simultaneous tasks, clock
speed only represents one facet of one component and is not
enough to measure the real performance of the entire system.
IDC OPINION
Accordingly, processor designs
evolved, but not merely by scaling the
clock speed.
– 3 – Is Megahertz Enough?
ing point units, and introduced more efficient techniques of data processing,
including adding more processing lines (pipelines) and processing
data and instructions to run the critical tasks first. Designers
also found ways to make processors work better in the context of the
entire system by introducing new instructions (e.g., MMX™ and
3DNow!™ Professional for multimedia) that were optimized for richer
data processing and by giving the processor a faster front-side bus
to the rest of the system.
Due to the different requirements of specific form factors and segments,
different processors from even the same vendor began to
deliver varied performance at the same clock rate. The issue
became more apparent when vendors like AMD moved to develop
their own architectures that, while still compatible with the x86
instruction set, took different approaches to maximize performance.
These approaches included changes that impacted both the processor
and the system (e.g., improved front-side buses).
Saturday, November 18, 2006
An Intro to Google File System
Designed and implemented the Google File System
(GFS) to meet the rapidly growing demands of Google’s
data processing needs. GFS shares many of the same goals
as previous distributed file systems such as performance,
scalability, reliability, and availability. However, its design
has been driven by key observations of our application workloads
and technological environment, both current and anticipated,
that reflect a marked departure from some earlier
file system design assumptions. We have reexamined traditional
choices and explored radically different points in the
design space.
First, component failures are the norm rather than the
exception. The file system consists of hundreds or even
thousands of storage machines built from inexpensive commodity
parts and is accessed by a comparable number of
client machines. The quantity and quality of the components
virtually guarantee that some are not functional at
any given time and some will not recover from their current
failures. We have seen problems caused by application
bugs, operating system bugs, human errors, and the failures
of disks, memory, connectors, networking, and power supplies.
Therefore, constant monitoring, error detection, fault
tolerance, and automatic recovery must be integral to the
system.
Second, files are huge by traditional standards. Multi-GB
files are common. Each file typically contains many application
objects such as web documents. When we are regularly
working with fast growing data sets of many TBs comprising
billions of objects, it is unwieldy to manage billions of approximately
KB-sized files even when the file system could
support it. As a result, design assumptions and parameters
such as I/O operation and blocksizes have to be revisited.
Third, most files are mutated by appending new data
rather than overwriting existing data. Random writes within
a file are practically non-existent. Once written, the files
are only read, and often only sequentially. A variety of
data share these characteristics. Some may constitute large
repositories that data analysis programs scan through. Some
may be data streams continuously generated by running applications.
Some may be archival data. Some may be intermediate
results produced on one machine and processed
on another, whether simultaneously or later in time. Given
this access pattern on huge files, appending becomes the focus
of performance optimization and atomicity guarantees,
while caching data blocks in the client loses its appeal.
Fourth, co-designing the applications and the file system
API benefits the overall system by increasing our flexibility.
For example, we have relaxed GFS’s consistency model to
vastly simplify the file system without imposing an onerous
burden on the applications. We have also introduced an
atomic append operation so that multiple clients can append
concurrently to a file without extra synchronization between
them. These will be discussed in more details later in the
paper.
Multiple GFS clusters are currently deployed for different
purposes. The largest ones have over 1000 storage nodes,
over 300 TB of diskst orage, and are heavily accessed by
hundreds of clients on distinct machines on a continuous
basis.
(GFS) to meet the rapidly growing demands of Google’s
data processing needs. GFS shares many of the same goals
as previous distributed file systems such as performance,
scalability, reliability, and availability. However, its design
has been driven by key observations of our application workloads
and technological environment, both current and anticipated,
that reflect a marked departure from some earlier
file system design assumptions. We have reexamined traditional
choices and explored radically different points in the
design space.
First, component failures are the norm rather than the
exception. The file system consists of hundreds or even
thousands of storage machines built from inexpensive commodity
parts and is accessed by a comparable number of
client machines. The quantity and quality of the components
virtually guarantee that some are not functional at
any given time and some will not recover from their current
failures. We have seen problems caused by application
bugs, operating system bugs, human errors, and the failures
of disks, memory, connectors, networking, and power supplies.
Therefore, constant monitoring, error detection, fault
tolerance, and automatic recovery must be integral to the
system.
Second, files are huge by traditional standards. Multi-GB
files are common. Each file typically contains many application
objects such as web documents. When we are regularly
working with fast growing data sets of many TBs comprising
billions of objects, it is unwieldy to manage billions of approximately
KB-sized files even when the file system could
support it. As a result, design assumptions and parameters
such as I/O operation and blocksizes have to be revisited.
Third, most files are mutated by appending new data
rather than overwriting existing data. Random writes within
a file are practically non-existent. Once written, the files
are only read, and often only sequentially. A variety of
data share these characteristics. Some may constitute large
repositories that data analysis programs scan through. Some
may be data streams continuously generated by running applications.
Some may be archival data. Some may be intermediate
results produced on one machine and processed
on another, whether simultaneously or later in time. Given
this access pattern on huge files, appending becomes the focus
of performance optimization and atomicity guarantees,
while caching data blocks in the client loses its appeal.
Fourth, co-designing the applications and the file system
API benefits the overall system by increasing our flexibility.
For example, we have relaxed GFS’s consistency model to
vastly simplify the file system without imposing an onerous
burden on the applications. We have also introduced an
atomic append operation so that multiple clients can append
concurrently to a file without extra synchronization between
them. These will be discussed in more details later in the
paper.
Multiple GFS clusters are currently deployed for different
purposes. The largest ones have over 1000 storage nodes,
over 300 TB of diskst orage, and are heavily accessed by
hundreds of clients on distinct machines on a continuous
basis.
Thursday, November 16, 2006
Coolest doubt in Mahabharat
In some remote village of India , one masterji is
teaching the
Mahabharat katha to class 6 students.
He is at the krishnajanma' part of it. Masterji:
"Kansa heard the
akashwani that his sister's 8th child is going to kill
him.
He was furious. He ordered to put vasudev n devki
behind the bars.
First son is born, and kansa kills him by poisoning...
Second one is born n kansa throws him off the mountain
peak. Third one
is born." Now Ramu, who is smartest of the lot, puts
up his hand.
Masterji, I have a doubt (sounding nervous n confused)
Masterji: "Ramu bete, whole India does not have doubt
in Mahabharata
then how come u have one?"
Ramu : Masterji, if Kansa knew that Devaki's 8th child
was going to
kill
him,
WHY THE HELL DID HE PUT VASUDEV AND DEVAKI IN THE SAME
CELL ?
Masterji fainted.........................
In some remote village of India , one masterji is
teaching the
Mahabharat katha to class 6 students.
He is at the krishnajanma' part of it. Masterji:
"Kansa heard the
akashwani that his sister's 8th child is going to kill
him.
He was furious. He ordered to put vasudev n devki
behind the bars.
First son is born, and kansa kills him by poisoning...
Second one is born n kansa throws him off the mountain
peak. Third one
is born." Now Ramu, who is smartest of the lot, puts
up his hand.
Masterji, I have a doubt (sounding nervous n confused)
Masterji: "Ramu bete, whole India does not have doubt
in Mahabharata
then how come u have one?"
Ramu : Masterji, if Kansa knew that Devaki's 8th child
was going to
kill
him,
WHY THE HELL DID HE PUT VASUDEV AND DEVAKI IN THE SAME
CELL ?
Masterji fainted.........................
Friday, November 10, 2006
Ambition(in general)
An ambition is an eager, and sometimes an inordinate, desire for preferment, honor, superiority, power, or the attainment of something. To obtain object or goal that is immensely desired. It comes from the Middle English word “ambicioun,” meaning and excessive desire for power, money or wealth. Ambition is something that everyone, no matter their age or cultural background, has instinctively. Ambition can be a driving force for success, or in some cases a road to failure. Through ambitious undertakings we can set goals and find ourselves and our God-given talents.
We are told never to cross a bridge until we come to it, but this world is owned by men who have 'crossed bridges' in their imagination far ahead of the crowd. I was watching the Doctor Phil Show the other day, and he was talking about the five reasons for why successful people are as successful as they are. Number one on the list was a plan. A goal. A destination. An ambition. Without an ambition we have no purpose in our lives. In contrast, a goal can help us get organized and take steps towards achieving what we want in our day-to-day lives. My friend Ryan always used to tell me, and still does; “My life's ambition is to be happy with my place in, and contribution to Society.” That might be a nice thought, but is there really a workable goal there? No! “The ambitious man is essentially a visualizer and an actualizer... He can visualize something, and when he visualizes it he sees exactly how to make it happen.” - Robert L. Schwartz A person who aims at nothing is sure to hit it. We were given a brain for a reason, and this is a perfect excuse to use it.
Keep away from people who try to belittle your ambitions. Small people always do that, but the really great make you feel that you, too, can become great. Following ones dreams and not giving a second thought to the comment of the people who put us down is what creates a successful entrepreneur. Spending time with people with a positive image and attitude can help one get motivated and realize their goals. Persistence can make everything possible, for persistence is an excellent demonstration of ambition. If one wants something to happen, one must, as a singer one put it, ‘pick themselves up and try again.’ Nothing will ever be just handed to anyone, except the odd exception.
In William Shakespeare’s Macbeth we can see how ambition can lead to devastating effect if our destination is reached by cheating. In general, concentrating on a false goal seems to cause far too much collateral damage to relationships and to self esteem. This is not to say that Macbeth’s ambition –to become king- was false. However he should have won this honor truthfully. Instead of earning the right respectfully, he stole it. Not only will this rout not be rewarding, for satisfaction is not gained, but it may cause paranoia leading to more of the same. Once one gets into this ever repeating chain the chance of getting out is a rocky road.
There is nothing that can stop us from achieving what we want in life. Our only obstacle is ourselves, and the extent of our ability to differentiate between a worthwhile and self destructive goal. If you can imagine it, you can achieve it. If you can dream it, you can become it. Don’t steal a vehicle, but use your own, and no matter what road you take, you will end up where you wanted to be.
We are told never to cross a bridge until we come to it, but this world is owned by men who have 'crossed bridges' in their imagination far ahead of the crowd. I was watching the Doctor Phil Show the other day, and he was talking about the five reasons for why successful people are as successful as they are. Number one on the list was a plan. A goal. A destination. An ambition. Without an ambition we have no purpose in our lives. In contrast, a goal can help us get organized and take steps towards achieving what we want in our day-to-day lives. My friend Ryan always used to tell me, and still does; “My life's ambition is to be happy with my place in, and contribution to Society.” That might be a nice thought, but is there really a workable goal there? No! “The ambitious man is essentially a visualizer and an actualizer... He can visualize something, and when he visualizes it he sees exactly how to make it happen.” - Robert L. Schwartz A person who aims at nothing is sure to hit it. We were given a brain for a reason, and this is a perfect excuse to use it.
Keep away from people who try to belittle your ambitions. Small people always do that, but the really great make you feel that you, too, can become great. Following ones dreams and not giving a second thought to the comment of the people who put us down is what creates a successful entrepreneur. Spending time with people with a positive image and attitude can help one get motivated and realize their goals. Persistence can make everything possible, for persistence is an excellent demonstration of ambition. If one wants something to happen, one must, as a singer one put it, ‘pick themselves up and try again.’ Nothing will ever be just handed to anyone, except the odd exception.
In William Shakespeare’s Macbeth we can see how ambition can lead to devastating effect if our destination is reached by cheating. In general, concentrating on a false goal seems to cause far too much collateral damage to relationships and to self esteem. This is not to say that Macbeth’s ambition –to become king- was false. However he should have won this honor truthfully. Instead of earning the right respectfully, he stole it. Not only will this rout not be rewarding, for satisfaction is not gained, but it may cause paranoia leading to more of the same. Once one gets into this ever repeating chain the chance of getting out is a rocky road.
There is nothing that can stop us from achieving what we want in life. Our only obstacle is ourselves, and the extent of our ability to differentiate between a worthwhile and self destructive goal. If you can imagine it, you can achieve it. If you can dream it, you can become it. Don’t steal a vehicle, but use your own, and no matter what road you take, you will end up where you wanted to be.
Wednesday, November 08, 2006
I just wanted to say few words.Just out of curiosity people who might visit my site may feel like knowing me.Its hard to know somebody but atleast you can have a perception.
A very simple guy who likes things to be simple and take them as they come.A strong believer in destiny as i feel it changes lifes..A die hard passion for cricket,Badminton.From the career aspect, working in Wipro Technologies.What else ,oh bye the way its me in the picture.After a long hard day.
Subscribe to:
Posts (Atom)
