Oke nvme SSD. thx

Oke nvme SSD. thx

Attached: 62ac5b7231ed13cebd6e52cacce9c2ae.png (437x232, 8K)

Other urls found in this thread:

gitlab.gnome.org/GNOME/vte/blob/master/perf/img.sh
twitter.com/AnonBabble

Oke Windows. thx microsoft

Oke OP. thx op

Small files always bring down the speed in any drive.

>90k files
idiot
also
>windows

What am I looking at? Do Windows users really use a GUI to copy files?

t. terminal autist
Why waste time typing out paths and commands when it's easier to use a gui?

>cp file copy
Done.

ctrl+a
ctrl+v

Done.

>he has to type directories
What is this, 1992?

>not rsync
shiggy

Because you have fine-grained control (e.g. exclude certain files/directories) and can use superior tools instead of whatever garbage implementation the GUI uses.

Why doesn't rsync --progress/-P default to total transfer progress instead of per-file? Per file is useless for small files because they get copied so quickly, and it's annoying to have to specify --info=progress2 or alias it.

>alias it.
just do this

more like
cp /home/user/.config/program/thing /home/user/docs/subdir/thing
instead of ctrl c, ctrl v

Attached: mitäs helkkaria.jpg (1080x1080, 73K)

Actually you can blame NTFS for this, because even with a speedy ssd it'll still chug, just not as much as a regular hard drive.

How often do you need fine-grained control?

Wow, so why don't you just use a better filesystem?

Attached: 1417936176191.png (811x710, 527K)

Can you do this on a gui?
cp dir/file otherdir/copy otherdir1/copy1 otherdir2/copy2 otherdir3/copy3
Also there's a thing called tab completion.

>Windows
>filesystem choice

Attached: aug_10_09_27_.jpg (992x788, 169K)

more like
>cp /p*TAB*/to/dir*TAB*/fil*GLOB* /dest*TAB*/doc*TAB*
instead of
>C:/ *click* *load* *look for next directory*
>/path *click* *load* *look for next directory*
>/to *click* *load* *look for next directory*
>/directory *click* *load* *look for next directory*
>*search* *glob*
>Ctrl+A
>Ctrl+C
>C:/ *click* *look for next directory*
>/destination *click* *look for next directory*
>/documents *click*
>Ctrl+V
>*error copying first file*
>*repeat*

>*load*
How old is your harddrive that this is long enough to be an inconvenience? Also how is looking for your next directory any different from ls? And if you frequent the folder you go to, you generally don't have to look for it.

What is a network filesystem?
also
>looking for your next directory any different from ls
Do you really cd then ls in every directory to build your path? lmao what a retard
>if you frequent the folder
Yeah I totally move around the same directory every day lmao

Attached: photo_2018-10-22_09-28-33.jpg (814x1280, 78K)

>That pic
Based

>Do you really cd then ls in every directory to build your path?
If I don't know the exact path, then yes. How else?

you're looking at things? online? what are you doing using a GUI you fag?

There is ReFS but no your not allowed that unless you have enterprise and even then you can't use it as a boot drive yet

I dunno, shell autocompletion?

Ya its pretty gay, just like windows in general

*pushes glasses up*

aaaaaaccchhhtttuuuually, it's got nothing to do with the file-system, it's because it's a lot of small files.

GUI is superior in certain cases. Say you have 100 files in a folder and each file is named different and has 10 letters. Now you need to copy and paste 30 of those files to another folder. Are you going to type out every single file into a long command line and likely fuck up a few letters or use your mouse and select the files you're copying?

>onion boy approaches the arena
Actually its because the NTFS filesystem isn't good with handling a ton of small files.

Are you copying both from and to an SSD? When I'm doing SSD-to-SSD copies, they're much faster than that, but SSD-to-HD and vice versa are still limited by the HD.
I just duplicated my Firefox profile folder on windows, which was 600 MB and 7000 files, and it was done in ~30 seconds. Using a WD Black 256GB for reference.
Surprisingly, when I tried it on my 2015 MBP, it took more like 5-10 seconds for a similar folder (10,000 files/500MB).

Like images, you mean? If there's a pattern, you can just match filenames for those you want. Otherwise, if the names are random and the only way to distinguish your 30 files is visually, then the smart thing to do is to not name them randomly in the first place, or have the in separate identifying folders.
This has less to do with the superiority of the GUI (its use is incidental here) but rather the superiority of the brain and visual processing.

that's what you get with tlc and shit IO

nah, you're autistic

>90k files
Nice shitpost

NVME drives are not automatically fast just because they fit in a NVME slot

I uses an ncurses browser and view images using this script: gitlab.gnome.org/GNOME/vte/blob/master/perf/img.sh

Does this level of efficiency make you mad?

Attached: Screenshot_2018-11-14_18-24-39.png (800x872, 31K)

lmao, I bet you are virgin too

Thanks NTFS

>alias it
>takes less than 15 seconds
Friendo its there for a reason
JUST DO IT YA GOOBER!!