I think the 1TB/day was additional data transferred, not total.
Yup, you're right, they've been hit by overwhelming 8 TB/day. The point (still true) is that that amount of data was hadled by whole pod with cumulative data throughput of at least 350 TB / day. And that, while not large enough to hold 8 TB data, any of those drives is capable of such daily average data rate, thus the difference in average datarate thrown at pods of different HDDs is not showing the difference in performance of those drives at all.
Do the maths. You can get 1TB 7200 RPM drive for... say 60$. 1TB SSD costs you from 350$ upwards (that's at newegg's). The power consumption of typical HDD is around 6W and depending on electricity rate (at my place it's around 25c/kWh) it takes around 22 years to burn enough electricity to cover the drive price difference. And with larger single drive sizes this comparison gets even worse for SSD.
The only reason to ditch HDDs in favour of SSDs is performance. If you only use your data at low speed (such as streaming single Blu-ray video at 54Mbps), any semi-modern HDD will do.
- Energy Use â" The Seagate drives were 7200 rpm and used slightly more electricity than the Western Digital drives which were 5400 rpm. This small difference adds up when you place 45 drives in a Storage Pod and then stack 10 Storage Pods in a cabinet.
- Loading speed â" Edge to Western Digital, by a little over 1 TB per day on average.
That didn't really make sense to me that the 5400 RPM drive beat out the 7200 RPM drive, so I did a bit of research.
How about some elementary arithmetics instead?
1TB of data per day on average boils down to neighbourhood of 11.5MB per second. I doubt that you are currently able to purchase a hard drive that can't sustain writes at several times higher speed. And that's single drive write performance while beforementioned 1TB data did hit whole Pod and was presumably spread over all of drives in the Pod. Hence the figure 1TB daily data is not showing any kind of performance limits...
More likely the meaning of 1TB daily data was that both test pods got hit by similar amount of data which is not showing the speed difference but rather showing that drives were not idle and thus the nil failure rate was a result which can be achieved under moderate load (things do tend to break under load more often).
OOP is, IMHO, over-rated. And you can use whatever you want from bash if built-in functionality is not (good) enough for you... just as you can use.NET from powershell.
And don't whine at the syntax, bash inherits legacy from Thompson shell (yup, that's Ken Thompson we're talking about) via Bourne shell. And that legacy starts in 1971. And legacy is good for many things.
If you want smething more modern, you're free to use whatever interpereter language (perl, python, Tcl, Erlang, Ruby, PHP, Emacs, TeX,...) as your default command line interpreter.
Neither the X station nor the dumb terminal "receive pre-rendered content".
You're not entirely right. They both receive partly pre-rendered content. Dumb terminals receive data about which character they need to display at certain (relative) screen location, however the shape of characters is done by terminals. X terminals receive parts of display content pre-rendered as bitmaps, they don't invent any of contents. Indeed they don't receive exact display contents in full and every time (eg. acording to refresh rate), they need to re-assemble full display content from incremental updates received from the mainframe/X client...
And for years, Linux was still the only mainstream OS that had good 64-bit support. The only thing holding users back were a couple of proprietary desktop applications that are now finally becoming fully obsolete. System administrators have been able to run full 64-bit Linux on their servers for what, 8 years or so.
Back in year 1999 (yup, that's full 13 years ago) I was using my desktop Linux (Red Hat Linux 5.1) on DEC alpha, which was fully 64-bit kernel and user space. We've been running Linux on some seroius DEC alpha machines instead of running DEC's own UNIX implementation (OSF/1) because it actually behaved better.
After I changed my employer in 2002, I had to downgrade to i386 version (being much more stable than amd64 at the time).
In Europe, EU commission passed a decree that we'll also have digital dividend. Frequencies between 790 and 862 MHz will be freed of TV and will be (in some countries already have been) sold for 4G mobile networks. It's a good thing that EC required that... in some countries (mine included) those frequencies would have remained in (D)TV domain.
Somewhat tangential, but are there dialects/programming languages in your locale that use semicolons to separate parameters in method invocations?
I wouldn't know. I'm not huge fan of CS translations and localizations, at least of those that go beyond proper localized output of data (numbers, dates). I've seen examples of actually translated programming language (Pascal to be exact) which made me sick. Which means that whenever I do programming I end up typing comma as parameter separator and dot as decimal separator. I hate using localized version of OS (Linux or Windows) that backfires me while using its calculator...
Also, the use of semicolons to separate function arguments is an annoying difference from Excel. Why not just use the same format? Was it patented? Most of the rest of the UI tries to be Excel-like... so why this difference?
Actually my Excel uses semicolons to separate function arguments. I always wonder why all examples in FAQs, Tutorials etc. insist on commas?
Really: everybody that uses comma as decimal sign (think Germany and remember StarDivision) use semicolon as separator sign. I guess OOo devels just adopted it as default/only option not to mess with different locales.
Ah well I think I understand how things work over there.
arkane1234 said that "I'm not understanding how American's are gettign the short end of the stick.". It's not that Americans are not bitten by their cellular market and players thereof. It's that elsewhere the stick being used on customers backs is much longer and thus customers' backs hurt much more.
That's what AC above was trying to say: Americans can buy cheap phones and cheap subscription plans and they still complain.
The rest of the world buy the same devices quite more expensive (unsubsidized gadgets usually cost in Europe the same amount of money as in US while currency in Europe is currently slightly higer valued that the one in US) and also other details about subscription plans are mostly less user-friendly.
If you use UPS, you'll need to do some re-transmits due to damaged packets. Due to long RTT (3 days forward, 5 hours back over phone call) it'll extend needed time to a couple of weeks...
The Lenny installer runs circles around the Ubuntu installer. Among other cool details you can configure LVM, or software raids prior to the disk formatting and installation.
Ubuntu Server Edition installer also allows you to configure SW RAID and LVM. It's just Ubuntu Desktop Edition that makes things easy for lusers.
One problem: SETS demands at least 50 amps current. Which is by standards in my countr quite a lot. No way that it much less with microwave technology. And this is the main reason for having water heaters with tanks: you can use low-power (say 6 or 10 amps) heating element and heat water in advance.
ATA disks are cheaper to manufacture than SCSI or Fibre Channel drives for several reasons.
One really huge difference lies also in electronics. Usually it's called SCSI Control Blocks (short: SCB's). They are actually commands, sent from SCSI controller to devices telling them what to do (read or write data, etc.)
Any decent SCSI drive will support at least 32 of them and it will execute them out of order, mostly optimizing head-movements. Which gives huge performance boost under truely multi-tasking system.
There exist critical radar systems for civilian and military air traffic control, as well as weather radar that CAN'T change the frequencies they are operating on.
See, weather radars actually can't change operating frequencies as this would be counter productive from physics' point of view. The wavelength (which is inversely proportional to frequency) used is closely correlated to the diameter of raindrops one eventually wants to detect. That means there's no real freedom choosing the frequency a weather radar operates.
Now, if the WiFi geeks would find a way to make the falling raindrops smaller, the weather guys would be happy to change the frequency of their radars.
Slashdot Mirror
It should work fine on Windows 3.11 running as a MS Basic program.
Actually, one could write a simple batch command file and run it under MS-DOS 3.30 or something. Nobody will touch it, hence no need for GUI.
I think the 1TB/day was additional data transferred, not total.
Yup, you're right, they've been hit by overwhelming 8 TB/day. The point (still true) is that that amount of data was hadled by whole pod with cumulative data throughput of at least 350 TB / day. And that, while not large enough to hold 8 TB data, any of those drives is capable of such daily average data rate, thus the difference in average datarate thrown at pods of different HDDs is not showing the difference in performance of those drives at all.
Do the maths. You can get 1TB 7200 RPM drive for ... say 60$. 1TB SSD costs you from 350$ upwards (that's at newegg's). The power consumption of typical HDD is around 6W and depending on electricity rate (at my place it's around 25c/kWh) it takes around 22 years to burn enough electricity to cover the drive price difference. And with larger single drive sizes this comparison gets even worse for SSD.
The only reason to ditch HDDs in favour of SSDs is performance. If you only use your data at low speed (such as streaming single Blu-ray video at 54Mbps), any semi-modern HDD will do.
That didn't really make sense to me that the 5400 RPM drive beat out the 7200 RPM drive, so I did a bit of research.
How about some elementary arithmetics instead?
1TB of data per day on average boils down to neighbourhood of 11.5MB per second. I doubt that you are currently able to purchase a hard drive that can't sustain writes at several times higher speed. And that's single drive write performance while beforementioned 1TB data did hit whole Pod and was presumably spread over all of drives in the Pod. Hence the figure 1TB daily data is not showing any kind of performance limits ...
More likely the meaning of 1TB daily data was that both test pods got hit by similar amount of data which is not showing the speed difference but rather showing that drives were not idle and thus the nil failure rate was a result which can be achieved under moderate load (things do tend to break under load more often).
OOP is, IMHO, over-rated. And you can use whatever you want from bash if built-in functionality is not (good) enough for you ... just as you can use .NET from powershell.
...) as your default command line interpreter.
And don't whine at the syntax, bash inherits legacy from Thompson shell (yup, that's Ken Thompson we're talking about) via Bourne shell. And that legacy starts in 1971. And legacy is good for many things.
If you want smething more modern, you're free to use whatever interpereter language (perl, python, Tcl, Erlang, Ruby, PHP, Emacs, TeX,
... which allies exactly? Germany? France?
Neither the X station nor the dumb terminal "receive pre-rendered content".
You're not entirely right. They both receive partly pre-rendered content. Dumb terminals receive data about which character they need to display at certain (relative) screen location, however the shape of characters is done by terminals. X terminals receive parts of display content pre-rendered as bitmaps, they don't invent any of contents. Indeed they don't receive exact display contents in full and every time (eg. acording to refresh rate), they need to re-assemble full display content from incremental updates received from the mainframe/X client ...
And for years, Linux was still the only mainstream OS that had good 64-bit support. The only thing holding users back were a couple of proprietary desktop applications that are now finally becoming fully obsolete. System administrators have been able to run full 64-bit Linux on their servers for what, 8 years or so.
Back in year 1999 (yup, that's full 13 years ago) I was using my desktop Linux (Red Hat Linux 5.1) on DEC alpha, which was fully 64-bit kernel and user space. We've been running Linux on some seroius DEC alpha machines instead of running DEC's own UNIX implementation (OSF/1) because it actually behaved better.
After I changed my employer in 2002, I had to downgrade to i386 version (being much more stable than amd64 at the time).
If the global economy wasn't in such a precarious state, gas would be over $5/gallon *now*! In 2032, $10/gallon gas will be a fond memory.
Talk about US petrol prices. In Europe, petrol price is in vicinity of 1.50€ per litre (likely even more), which is in neighbourhood of $7/gallon.
Exactly. So killing everyone's battery isn't due to P2P back-end. Unless smoke is caused by battery being killed.
What exactly is P2P back-end?
In Europe, EU commission passed a decree that we'll also have digital dividend. Frequencies between 790 and 862 MHz will be freed of TV and will be (in some countries already have been) sold for 4G mobile networks. It's a good thing that EC required that ... in some countries (mine included) those frequencies would have remained in (D)TV domain.
Yup, I was implying that I code in English, I just try to make output correctly localized where applicable.
Somewhat tangential, but are there dialects/programming languages in your locale that use semicolons to separate parameters in method invocations?
I wouldn't know. I'm not huge fan of CS translations and localizations, at least of those that go beyond proper localized output of data (numbers, dates). I've seen examples of actually translated programming language (Pascal to be exact) which made me sick. Which means that whenever I do programming I end up typing comma as parameter separator and dot as decimal separator. I hate using localized version of OS (Linux or Windows) that backfires me while using its calculator ...
Also, the use of semicolons to separate function arguments is an annoying difference from Excel. Why not just use the same format? Was it patented? Most of the rest of the UI tries to be Excel-like... so why this difference?
Actually my Excel uses semicolons to separate function arguments. I always wonder why all examples in FAQs, Tutorials etc. insist on commas? Really: everybody that uses comma as decimal sign (think Germany and remember StarDivision) use semicolon as separator sign. I guess OOo devels just adopted it as default/only option not to mess with different locales.
Ah well I think I understand how things work over there.
arkane1234 said that "I'm not understanding how American's are gettign the short end of the stick.". It's not that Americans are not bitten by their cellular market and players thereof. It's that elsewhere the stick being used on customers backs is much longer and thus customers' backs hurt much more.
That's what AC above was trying to say: Americans can buy cheap phones and cheap subscription plans and they still complain.
The rest of the world buy the same devices quite more expensive (unsubsidized gadgets usually cost in Europe the same amount of money as in US while currency in Europe is currently slightly higer valued that the one in US) and also other details about subscription plans are mostly less user-friendly.
If you use UPS, you'll need to do some re-transmits due to damaged packets. Due to long RTT (3 days forward, 5 hours back over phone call) it'll extend needed time to a couple of weeks ...
The Lenny installer runs circles around the Ubuntu installer. Among other cool details you can configure LVM, or software raids prior to the disk formatting and installation.
Ubuntu Server Edition installer also allows you to configure SW RAID and LVM. It's just Ubuntu Desktop Edition that makes things easy for lusers.
One problem: SETS demands at least 50 amps current. Which is by standards in my countr quite a lot. No way that it much less with microwave technology. And this is the main reason for having water heaters with tanks: you can use low-power (say 6 or 10 amps) heating element and heat water in advance.
ATA disks are cheaper to manufacture than SCSI or Fibre Channel drives for several reasons.
One really huge difference lies also in electronics. Usually it's called SCSI Control Blocks (short: SCB's). They are actually commands, sent from SCSI controller to devices telling them what to do (read or write data, etc.)
Any decent SCSI drive will support at least 32 of them and it will execute them out of order, mostly optimizing head-movements. Which gives huge performance boost under truely multi-tasking system.
There exist critical radar systems for civilian and military air traffic control, as well as weather radar that CAN'T change the frequencies they are operating on.
See, weather radars actually can't change operating frequencies as this would be counter productive from physics' point of view. The wavelength (which is inversely proportional to frequency) used is closely correlated to the diameter of raindrops one eventually wants to detect. That means there's no real freedom choosing the frequency a weather radar operates.
Now, if the WiFi geeks would find a way to make the falling raindrops smaller, the weather guys would be happy to change the frequency of their radars.