Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nvme? #5

Open
dsrtusr88 opened this issue Feb 26, 2022 · 4 comments
Open

nvme? #5

dsrtusr88 opened this issue Feb 26, 2022 · 4 comments

Comments

@dsrtusr88
Copy link

Do you need to do anything for an NVME or is it smart enough to treat it differently from a SATA SSD?

@dsrtusr88
Copy link
Author

I ran the script as-is. In my case, I have a SATA SSD 2TB and an NVME SSD 1 TB. It set the SATA SSD utilization capped at 1TB for the NVME, is there a way around this?

@freemansoft
Copy link
Owner

I don't have a system with a spare NVME drive so I don't have a way to test.

You have two drives, one SATA 2TB and one NVME 1TB, correct?

@dsrtusr88
Copy link
Author

that's correct, from your notes, it sounds like they're stuck at which ever drive is smallest?

@freemansoft
Copy link
Owner

Just saw that you are talking all SSDs. The code exists to use an SSD as a cache for slower spinning disks. I'm not sure there is any speed advantage using an NVME in front of SSDs.

The code specifically picks out drives by type. I didn't code for an NVME so it probably isn't going to work. It assumes the SATA SSDs are the cache and other drives are the slow drives. It may be assuming your NVME is a slow drive so the max it could handle is 1TB.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants