You're supposed to disable this crap on SSDs, right? Why does Winblows enable it anyway? Both 7 and 10 LTSB1607 do this

You're supposed to disable this crap on SSDs, right? Why does Winblows enable it anyway? Both 7 and 10 LTSB1607 do this.

Attached: defrag.png (715x513, 16K)

Other urls found in this thread:

en.wikipedia.org/wiki/Trim_(computing)
twitter.com/SFWRedditImages

Yes, yes... Disable it... It's ok if you're gonna need new SSD sooner...

>1607
Found your problem.

HAHAHA, YES!

1809 LTSC does the same shit.

install gentoo

No, you not supposed to disable trim. Jesus.

Windows doesn't defragment SSDs, it does something else. You should turn it on.

I am running 1809 LTSC and it's not enabled and never hasn't been since I installed it.

> Windows doesn't defragment SSDs, it does something else.
Yeah, it's called trim.

You don't know what you're talkking about.

>it does something else
Such as?

Attached: Untitled.png (1040x630, 195K)

I ran it manually and it says that it "trimmed" the SSD.

en.wikipedia.org/wiki/Trim_(computing)
If you don't regularly run the trim command, your SSDs will wear down much faster, that's the gist of it. Windows takes care of that for you.

That screenshot shows you trim is enabled. defrag.exe has nothing to do with trim.

Windows is trimming your SSD, not defragment

It's not "defrag.exe." It's a scheduler that trims SSDs and defrags HDs.

See

Are you dumb? It says optimize, not defragment, because it doesn't defragment them

Are you dumb? Can't you read that trim is enabled?

> As far as Retrim is concerned, this command should run on the schedule specified in the dfrgui UI. Retrim is necessary because of the way TRIM is processed in the file systems. Due to the varying performance of hardware responding to TRIM, TRIM is processed asynchronously by the file system. When a file is deleted or space is otherwise freed, the file system queues the trim request to be processed. To limit the peek resource usage this queue may only grow to a maximum number of trim requests. If the queue is of max size, incoming TRIM requests may be dropped. This is okay because we will periodically come through and do a Retrim with Storage Optimizer. The Retrim is done at a granularity that should avoid hitting the maximum TRIM request queue size where TRIMs are dropped.

He's right you dipshit don't disable TRIM.

Retard lol

>look into services in Win 7 control panel
>Disk Defragmenter disabled entirely
>Superfetch set to manual start, not running
What's the issue again?

Defragmenting ssds means moving files into one flash block (usually 128kB). It's always read at once anyway, so that way you get faster access + more free (trimmed) 128kB flash sectors.
A 128kB file can be fragmented into 2x64kB in two different sectors (each will have 64kB of pointless trash data) or one 128kB sector.

>Why does Winblows enable it anyway? Both 7 and 10 LTSB1607 do this.
Because its trimming not defrag retard

>ITT: People fighting his "OS" so it doesn't destroy its hardware

Attached: 1523272274489_0.gif (640x358, 1.94M)

No, Windows doesn't defrag SSDs. It just trims them, which you should not disable.

>ITT: People fighting his "OS" so it doesn't save and care for its hardware
fixed for you

/thread

Attached: defag.png (490x46, 3K)

kys lol

>toshiba ssd
BASED

Kys yourself retard.

kys autistic fat fuck!