New computer, but when?

Message boards : Number crunching : New computer, but when?
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3

AuthorMessage
HTH
Volunteer tester

Send message
Joined: 8 Jul 00
Posts: 691
Credit: 909,237
RAC: 0
Finland
Message 826512 - Posted: 3 Nov 2008, 12:33:53 UTC
Last modified: 3 Nov 2008, 12:55:16 UTC

Some calculations will follow.

If one has 8 gigabytes (8192 MB) of RAM and one wants to hibernate his/her Windows, it will take 8192 MB / 250 MB/s = about 33 seconds to write that amount of data to the Intel 32GB X-25E Extreme SATA Solid State Drive disk.

For comparsion, let's assume one's Hard Disk Drive writes 50 MB/s. It will take 8192 MB / 50 MB/s = about 164 seconds to hibernate! That is about 5 times the time it took for the SSD to write the same amount of data.

Not just the hibernation or booting time, SSD will make also chkdsk/scandisk, defrag and virus scanning faster. SSDs should also last years in a normal use and they will not crash like the HDDs do. They will slowly wear out and the available disk space should automatically go down (because the bad areas are no longer usable).

SSD is the future.

Henri.

Manned mission to Mars in 2019 Petition <-- Sign this, please.
ID: 826512 · Report as offensive
Profile dnolan
Avatar

Send message
Joined: 30 Aug 01
Posts: 1228
Credit: 47,779,411
RAC: 32
United States
Message 826560 - Posted: 3 Nov 2008, 15:00:26 UTC - in response to Message 826512.  


Not just the hibernation or booting time, SSD will make also chkdsk/scandisk, defrag and virus scanning faster. SSDs should also last years in a normal use and they will not crash like the HDDs do. They will slowly wear out and the available disk space should automatically go down (because the bad areas are no longer usable).


Can't remember where I saw it, but I believe defrag is not recommended for SSDs. Also, why would you want to hibernate with Seti (or Boinc) running?

-Dave
ID: 826560 · Report as offensive
HTH
Volunteer tester

Send message
Joined: 8 Jul 00
Posts: 691
Credit: 909,237
RAC: 0
Finland
Message 826567 - Posted: 3 Nov 2008, 15:21:01 UTC - in response to Message 826560.  
Last modified: 3 Nov 2008, 15:21:55 UTC

Can't remember where I saw it, but I believe defrag is not recommended for SSDs. Also, why would you want to hibernate with Seti (or Boinc) running?


One has to defrag every now and then or otherwise the filesystem will become very very slow (because the files are fragmented). Actually, I do not know is the fragmentation a problem in SSDs, because the latencies are very slow compared to HDDs. But I do not think that defragmenting, say, once a month is a problem in modern SSDs.

Why not to hibernate when running SETI@home? Hibernating is usually much faster than shutting down the computer (for the night) and the booting the machine (and Windows) again in the morning.

Henri.

Manned mission to Mars in 2019 Petition <-- Sign this, please.
ID: 826567 · Report as offensive
Profile dnolan
Avatar

Send message
Joined: 30 Aug 01
Posts: 1228
Credit: 47,779,411
RAC: 32
United States
Message 826576 - Posted: 3 Nov 2008, 15:36:27 UTC - in response to Message 826567.  


One has to defrag every now and then or otherwise the filesystem will become very very slow (because the files are fragmented). Actually, I do not know is the fragmentation a problem in SSDs, because the latencies are very slow compared to HDDs. But I do not think that defragmenting, say, once a month is a problem in modern SSDs.



Well, like I said, I can't remember where I read it, but here's one quote:
"Remember, these are solid-state devices, so the classical issue of data fragmentation that can occur on a rotating drive platter doesn't apply, due to the extremely high access time."

It's from a review here.


Why not to hibernate when running SETI@home? Hibernating is usually much faster than shutting down the computer (for the night) and the booting the machine (and Windows) again in the morning.

Henri.


The suggestion was tongue-in-cheek... a little joke.

-Dave
ID: 826576 · Report as offensive
HTH
Volunteer tester

Send message
Joined: 8 Jul 00
Posts: 691
Credit: 909,237
RAC: 0
Finland
Message 826582 - Posted: 3 Nov 2008, 16:08:10 UTC - in response to Message 826576.  

It's from a review here.

Thanks for the link.


Why not to hibernate when running SETI@home? Hibernating is usually much faster than shutting down the computer (for the night) and the booting the machine (and Windows) again in the morning.

The suggestion was tongue-in-cheek... a little joke.

Oh, I get it. :D

Henri.

Manned mission to Mars in 2019 Petition <-- Sign this, please.
ID: 826582 · Report as offensive
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 826701 - Posted: 3 Nov 2008, 21:38:56 UTC - in response to Message 826512.  

If one has 8 gigabytes (8192 MB) of RAM and one wants to hibernate his/her Windows, it will take 8192 MB / 250 MB/s = about 33 seconds to write that amount of data to the Intel 32GB X-25E Extreme SATA Solid State Drive disk.


I believe that's a theoretical write speed of the flash drive since 250MB/s is impossible with today's HDD controllers (and these SSD's plug into the SATA controller, correct?).

Not just the hibernation or booting time, SSD will make also chkdsk/scandisk, defrag and virus scanning faster. SSDs should also last years in a normal use and they will not crash like the HDDs do. They will slowly wear out and the available disk space should automatically go down (because the bad areas are no longer usable).

SSD is the future.


SSD may be the future, but not for the foreseeable future. HDDs have capacity, which is very important to many people out there, HDDs aren't as unreliable as people make them out to be (though a good backup is always recommended - even when using SSDs), and HDDs have the best price per gigabyte, and cost is everything in a capitalistic environment unless the task demands more.

Why not to hibernate when running SETI@home? Hibernating is usually much faster than shutting down the computer (for the night) and the booting the machine (and Windows) again in the morning.


Because I'd rather keep running the science. I don't hibernate any of my machines.
ID: 826701 · Report as offensive
HTH
Volunteer tester

Send message
Joined: 8 Jul 00
Posts: 691
Credit: 909,237
RAC: 0
Finland
Message 826728 - Posted: 3 Nov 2008, 22:14:54 UTC - in response to Message 826701.  
Last modified: 3 Nov 2008, 22:19:02 UTC

I believe that's a theoretical write speed of the flash drive since 250MB/s is impossible with today's HDD controllers (and these SSD's plug into the SATA controller, correct?).


Yes, but SATA II (or SATA 3.0 Gbit/s to be correct) should be able to transfer 300 megabytes per second. That should be enough for the Intel SSD. Of course, "SATA III" (or SATA 6.0 Gbit/s) is needed for even faster SSDs. That is why I wrote earlier:
- motherboard supporting Nehalem, USB 3, SATA 6.0 Gbit/s and UEFI


See this.

Henri.

Manned mission to Mars in 2019 Petition <-- Sign this, please.
ID: 826728 · Report as offensive
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 826744 - Posted: 3 Nov 2008, 22:38:04 UTC - in response to Message 826728.  

I believe that's a theoretical write speed of the flash drive since 250MB/s is impossible with today's HDD controllers (and these SSD's plug into the SATA controller, correct?).


Yes, but SATA II (or SATA 3.0 Gbit/s to be correct) should be able to transfer 300 megabytes per second. That should be enough for the Intel SSD. Of course, "SATA III" (or SATA 6.0 Gbit/s) is needed for even faster SSDs. That is why I wrote earlier:
- motherboard supporting Nehalem, USB 3, SATA 6.0 Gbit/s and UEFI


See this.

Henri.


SATA II's 3Gbit/s is a burst rate, not a sustained rate. Protocol overhead always keeps that number down.
ID: 826744 · Report as offensive
_heinz
Volunteer tester

Send message
Joined: 25 Feb 05
Posts: 744
Credit: 5,539,270
RAC: 0
France
Message 827526 - Posted: 6 Nov 2008, 9:03:04 UTC

there is a interesting article, maybe this helps clarify your questions

heinz
ID: 827526 · Report as offensive
HTH
Volunteer tester

Send message
Joined: 8 Jul 00
Posts: 691
Credit: 909,237
RAC: 0
Finland
Message 829618 - Posted: 12 Nov 2008, 14:31:41 UTC - in response to Message 826744.  

Hi!
SATA II's 3Gbit/s is a burst rate, not a sustained rate. Protocol overhead always keeps that number down.


http://en.wikipedia.org/wiki/Talk:Serial_ATA#Burst_rate_or_sustained_rate.3F

Henri.

Manned mission to Mars in 2019 Petition <-- Sign this, please.
ID: 829618 · Report as offensive
OzzFan Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 9 Apr 02
Posts: 15691
Credit: 84,761,841
RAC: 28
United States
Message 829741 - Posted: 13 Nov 2008, 3:12:45 UTC - in response to Message 829618.  

Hi!
SATA II's 3Gbit/s is a burst rate, not a sustained rate. Protocol overhead always keeps that number down.


http://en.wikipedia.org/wiki/Talk:Serial_ATA#Burst_rate_or_sustained_rate.3F

Henri.


I wouldn't trust those at Wikipedia to truly know what they're talking about, especially the one guy that says he thinks SSD drives can get up to 450MB/s. These are not necessarily people who have studied up on the technology, but casual internet users who like to pretend they know what they're talking about. This is one of the downsides to WikiPedia.

Every aspect of the computer, whether it is PCI, ISA, PATA, SATA, PCI-e, the Front Side Bus, the Backside Bus, AGP, even Intel's new QuickPath Interconnect - they all have protocol overhead, or in other words, part of the theoretical bandwidth is used up by electrical signals that verify the integrity of the payload being delivered, or that the data is delivered at all. These protocols are built into the spec itself when the spec is designed by engineers to ensure that data gets where its supposed to go, and follows a strict set of rules to get there, and that it actually gets there because no one likes lost data.

This is why no piece of hardware actually achieves full bandwidth saturation, and many times the bandwidth has to be shared with other devices, which add extra protocols to ensure the right data gets delivered to the right device.
ID: 829741 · Report as offensive
Keith White
Avatar

Send message
Joined: 29 May 99
Posts: 392
Credit: 13,035,233
RAC: 22
United States
Message 829913 - Posted: 13 Nov 2008, 20:00:31 UTC
Last modified: 13 Nov 2008, 20:28:32 UTC

3Gb/s SATA ~ 300MB/s

This is normally approachable in "burst" bandwidth benchmarks as the bandwidth of the internal drive cache. A number of disk benchmarking programs can test for this. I've not seen any exceed the theoretical 300MB/s of SATA 3.0Gb but I've seen some in the 250MB/s range.

Edit: Mechanical hard drives have a small amount of discrete cache memory, SSD drives don't. Didn't mean to imply they did.
"Life is just nature's way of keeping meat fresh." - The Doctor
ID: 829913 · Report as offensive
Previous · 1 · 2 · 3

Message boards : Number crunching : New computer, but when?


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.