Defrag

[ronnfigg]

Does the SSD in the Kronos ever require defragmenting, or does the technology not require it?

[lotty1]

Does the SSD in the Kronos ever require defragmenting, or does the technology not require it?

4
I believe the ssd can be destroyed by defragging it.
So I would not do it just my opinion.

[ronnfigg]

Does the SSD in the Kronos ever require defragmenting, or does the technology not require it?

Never mind, just googled the answer. I guess I should have done that first. But just in case anyone's interested here's the answer

http://www.pcworld.com/article/2047513/ ... r-ssd.html

[Diego5150]

Oooh that would have hurt.
Sorry for the stupid question (not that I would do it) but how were you going to defrag the hard drive on the Kronos?

[ronnfigg]

Oooh that would have hurt.
Sorry for the stupid question (not that I would do it) but how were you going to defrag the hard drive on the Kronos?

Well, first of all there is no hard drive (HDD) in the Kronos. There is a solid state drive (SSD). Secondly I know there is no utility on the Kronos to do this so I was curious if there would be a way. But being the process is not native to the Kronos I don't think I would try it any other way. But now after reading the website I will not try at all.

[michelkeijzers]

An SSD does not have to be defragged, because it has no benefits.

On a normal harddisc it is useful to put the information belonging together consequently, because of a 'hardware' reading arm. However the SSD does not have any movable parts and reading from 'location' X after Y is not other than location Z, even if X and Y and Z have different 'distances to eachother'.

Actually, it can even hurt to defrag, because there is a(quite high though) number of rewrites of each location. This means that if you write a location very many times, that single location will become unusable. However, a typical defrag algorithm will read/write (actually swap) very many locations, making the lifetime of an SSD shorter.

[Diego5150]

Oooh that would have hurt.
Sorry for the stupid question (not that I would do it) but how were you going to defrag the hard drive on the Kronos?

Well, first of all there is no hard drive (HDD) in the Kronos. There is a solid state drive (SSD). Secondly I know there is no utility on the Kronos to do this so I was curious if there would be a way. But being the process is not native to the Kronos I don't think I would try it any other way. But now after reading the website I will not try at all.

Obviously you took my question literally, my question was how would you defrag the drive being that there was no utility available? So maybe I should recant my statement that my question was stupid..........

[michelkeijzers]

Oooh that would have hurt.
Sorry for the stupid question (not that I would do it) but how were you going to defrag the hard drive on the Kronos?

Well, first of all there is no hard drive (HDD) in the Kronos. There is a solid state drive (SSD). Secondly I know there is no utility on the Kronos to do this so I was curious if there would be a way. But being the process is not native to the Kronos I don't think I would try it any other way. But now after reading the website I will not try at all.

Obviously you took my question literally, my question was how would you defrag the drive being that there was no utility available? So maybe I should recant my statement that my question was stupid..........

The question is not stupid at all. Because now you know more than before

[Diego5150]

Well, first of all there is no hard drive (HDD) in the Kronos. There is a solid state drive (SSD). Secondly I know there is no utility on the Kronos to do this so I was curious if there would be a way. But being the process is not native to the Kronos I don't think I would try it any other way. But now after reading the website I will not try at all.

Obviously you took my question literally, my question was how would you defrag the drive being that there was no utility available? So maybe I should recant my statement that my question was stupid..........

The question is not stupid at all. Because now you know more than before

I appreciate the response Michel, I agree that no question is stupid that is how we learn but I get a little annoyed when people come off with a bit of arrogance. I try to keep it light and although it may not have been intended to come off that way it aggravated me just a bit.

And unfortunately I did learn anything because my question of how the drive was going to defragmented was never answered.

[PianoManChuck]

That's a little disconcerting (I read the article provided in the earlier link) that its good for a few thousand write cycles. Not that the Kronos is doing a lot of writing to the SSD, but if you're even in a scenario where you're doing a lot of writing, it can actually be bad for the SSD?

[SanderXpander]

A few thousand may be misleading. It's more like 30.000 to 60.000 depending on the make and type. And that goes for each separate write location. It has a controller that makes sure data gets spread evenly as much as possible. The Kronos OS actually doesn't write at all to the SSD while it's running, quite opposed to "regular" computer OSs which do this constantly. The only times you're writing to the disk is when you're saving stuff or recording to disk. That means the rest of your Kronos is likely to crumble to dust before you reach the end of the SSD IOPS.

[Yuma]

That's a little disconcerting (I read the article provided in the earlier link) that its good for a few thousand write cycles. Not that the Kronos is doing a lot of writing to the SSD, but if you're even in a scenario where you're doing a lot of writing, it can actually be bad for the SSD?

Theoretically: yes.

As Sander wrote though, the maximum amount of write cycles before a sector becomes unavailable is tens of thousands.
I've read in a computer magazine that you could use an SSD in a PC, have that PC turned on 24/7 and work for 30 years
with it before the whole SSD has become unusable from write cycles.

In practice hard disk drives (HDD) break down much earlier, so no worries.

[PianoManChuck]

Thanks! I guess I really don't need to worry about it then, since I probably won't even be alive in 30 years!!! I'm sure I'll be replacing the Kronos with something else in the next 10 years (my Korg Triton Pro/x lasted me 11 years before I upgraded to the Kronos).

[jeebustrain]

The other big thing to consider is that the format is ext3, not NTFS or FAT. Windows/DOS filesystems use sequential writes to the disk sectors, allowing holes to be created when data is deleted. It then fills those holes with new data, creating file fragmentation if the new files don't fit neatly in that hole. This is why you need to defragment Windows systems.

ext2/3 use randomized block writes over the disk, essentially eliminating fragmentation until the disk is about 90% full. Once it reaches 90% capacity, the filesystem automatically starts rearranging data to make it contiguous. HFS+ (Apple) filesystems use the same process (along with some other neat tricks), which is why you don't need to defrag a Mac either.

[SanderXpander]

That's mostly a myth, or rather used to be true about FAT or very old drives using NTFS. On a Windows system with sufficient RAM, fragmentation and defragmentation has almost no effect on system performance.