F
Flasherly
put another one, ssd in
dos native transfers - no gain, if not pain, between ssd<>ssd
but it is a semi-intensive compression thingy I'm working with on
sector-to-sector binary transfers
ssd's are great, don't get me wrong, but at a certain point of
efficiency, they're redundant. Once the OS and supportive
applications layers are in NAND - it's only going so much farther.
may as well call it hybrid scenario then, as storage to cost
considerations mean a lot more when a $89 plattered 3T drive trumps
(for most) a $500 1T SSD.
Fortunately, I've got enough accumulated storage/data to where I can
say getting around in that quagmire is a lot easier on a SSD than
platters. (175G of storage still does take some time for eating up
CPU cycles while churning over indices and whatnot. Transfers, figure
I'm cutting time down somewhere between 1/2 and third of a
conventional drive trxs.)
As for my core OS, binary backups, one SSD pretty well covers about as
much speed as the OS is going to give up;- as mentioned, DOS binary
backups, well, it's in the header.
They're a lot of fun, though. Real pain in the butt to get this one -
had to fight it tooth and nail over getting the MBR settled,
(Partition Magic fixed it - 1st fat/primary for valid fdisk/format to
sys a: c: take, and last a boot arbitrator and that's pretty damn
nervey for probably a 10yr old prg!), some trouble with Win XP puking
over virtual memory (swapfile) assignments/cludge to get thru. Got
that thru another "settings" angle, luckily.
Haven't looked it over for what Win7 will think of my "new&improved
sys" yet.
This isn't a Samsung SSD unit, btw, like my other two. Samsungs are
pretty much effortless in my experience. Still this new brand, it's
working as expected with nothing major wrong - has a good reputation
for a somewhat smaller adherence, 3yr warrantee &etc., so enough said
about $20-25 average on 60G chunks of NAND.
That trim crap - can't believe after all these years they don't break
down and address some code directly to the controller. Was reading
some crap that for the controller otherwise to kick in its "garbage
routine" (independently of the non-TRIM OS) -- Log Out and let the
computer sit for 10 hours.
How about kiss my big hairy butt while I wait expressely for somebody
to address code directly to the controller;- besides, it may be NTFS
dependent for an OS TRIM request: screw TRIM for *nix and FAT
altogether, sounds like. And, little surprise, I can't stand NTFS
(except for what I'm stuck with using for - in case dealing in larger
than FAT32 allowances of 4G filesizes). That stuff about writing 1's
or 0's to clear the logic NAND gates, nahhh, don't like that either.
Only thing I got going for me, is once settled in, I don't need to
churn data, especially, and can just let it run 24/7, the way I like.
Got a big'un in between the SDD units, besides, big plattered drive if
I need to churn up some redundant read/write muck.
dos native transfers - no gain, if not pain, between ssd<>ssd
but it is a semi-intensive compression thingy I'm working with on
sector-to-sector binary transfers
ssd's are great, don't get me wrong, but at a certain point of
efficiency, they're redundant. Once the OS and supportive
applications layers are in NAND - it's only going so much farther.
may as well call it hybrid scenario then, as storage to cost
considerations mean a lot more when a $89 plattered 3T drive trumps
(for most) a $500 1T SSD.
Fortunately, I've got enough accumulated storage/data to where I can
say getting around in that quagmire is a lot easier on a SSD than
platters. (175G of storage still does take some time for eating up
CPU cycles while churning over indices and whatnot. Transfers, figure
I'm cutting time down somewhere between 1/2 and third of a
conventional drive trxs.)
As for my core OS, binary backups, one SSD pretty well covers about as
much speed as the OS is going to give up;- as mentioned, DOS binary
backups, well, it's in the header.
They're a lot of fun, though. Real pain in the butt to get this one -
had to fight it tooth and nail over getting the MBR settled,
(Partition Magic fixed it - 1st fat/primary for valid fdisk/format to
sys a: c: take, and last a boot arbitrator and that's pretty damn
nervey for probably a 10yr old prg!), some trouble with Win XP puking
over virtual memory (swapfile) assignments/cludge to get thru. Got
that thru another "settings" angle, luckily.
Haven't looked it over for what Win7 will think of my "new&improved
sys" yet.
This isn't a Samsung SSD unit, btw, like my other two. Samsungs are
pretty much effortless in my experience. Still this new brand, it's
working as expected with nothing major wrong - has a good reputation
for a somewhat smaller adherence, 3yr warrantee &etc., so enough said
about $20-25 average on 60G chunks of NAND.
That trim crap - can't believe after all these years they don't break
down and address some code directly to the controller. Was reading
some crap that for the controller otherwise to kick in its "garbage
routine" (independently of the non-TRIM OS) -- Log Out and let the
computer sit for 10 hours.
How about kiss my big hairy butt while I wait expressely for somebody
to address code directly to the controller;- besides, it may be NTFS
dependent for an OS TRIM request: screw TRIM for *nix and FAT
altogether, sounds like. And, little surprise, I can't stand NTFS
(except for what I'm stuck with using for - in case dealing in larger
than FAT32 allowances of 4G filesizes). That stuff about writing 1's
or 0's to clear the logic NAND gates, nahhh, don't like that either.
Only thing I got going for me, is once settled in, I don't need to
churn data, especially, and can just let it run 24/7, the way I like.
Got a big'un in between the SDD units, besides, big plattered drive if
I need to churn up some redundant read/write muck.