Hey

I wish to have my /cache on an SSD drive while the rest of the install is fine on a regular HD.

I'm looking for instructions on how this is done. Links or direct help welcome.

I assume there will be some editing of scripts for start-up

I often allocate large amounts of memory in my C programs for data so I want to place the cache on a dedicated SSD for faster I/O

I appreciate your help.

What exactly do you mean by 'cache' in this context? Might that be what I would call "swap space" or "swap partition"?

1 members found this post helpful.

Yes, I apologize I meant swap.

Once I realized my error I was able to see some results.

I am reading about parted https://access.redhat.com/documentat...k-storage.html
Another source talks about swapon, swapoff, editing /ect/fstab and using mkswap

There seems to be more than one way to get this done.

What I want to do is use a dedicated SSD for Swap
. From parted that drive is sdc here. From parted I see no disk flag number start and so on no data.
GParted shows unallocated partition unallocated filesystem for that SSD

I am guessing that one would comment out the fstab,delete the current swap partition and ???

High level: swap can be a file or a partition. Different techniques are used, but the concept is the same. Prep the space to be used as swap, activate the new swap, set the new swap to be available on startup and remove startup support for the old swap, release the old swap (on old kernels this required a reboot).

If this were a rotational drive, I would advise partitioning into a swap volume and a linux volume. That would give you very fast swap without dedicating the entire device to swap. Since it is SSD, you should be able to allocate the entire thing to storage and use the file swap technique without significant penalty.

Be aware, that most linux servers with sufficient ram do not normally use the swap, when they do they use it very intelligently. Swap is only there for continual use in the case ram is not sufficient for normal operation. When ram is sufficient, you allocate swap so that your system does not crash when it is under unusual stress. In your case it is important to have swap available, but I would not expect allocating swap to an SSD device to make a noticable performance difference.

There are online documents, how-to pages, and many resources online describing the steps you might follow, just be careful and do not mix them. Let me know if you get into trouble.

1 members found this post helpful.

Seems like a criminal waste of a SSD, but it's your choice.
Create a partition(s) on the device, run mkswap on each. Then run swapon for each to ensure they are recognised ok ("swapon -s" will show them). Then add them to fstab - comment out the old one. Done - simple.

You might be better off determining your swap rate - in particular the swapin rate, because that's really all you care about. Will the SSD really make that much difference in the grand scheme of things ?.

1 members found this post helpful.

Thanks. I will be working on this this coming weekend.

SSDs are not so expensive these days.
I'll try this and see if it makes working with very large data sets in C easier for me.
If nothing else it's an interesting learning experience for me.

Again my appreciation. Linux seems daunting at times.

I'll report back.

One thing you MIGHT do is not use tmpfs for /tmp. By default that can use up to 1/2 your memory. Making a real partition for it will free up that memory. Sometimes using an ssd for /tmp instead would work better.

You do get to clean it out though - the purpose of mount /tmp with tmpfs is that it is automatically cleaned out for you on every boot.

1 members found this post helpful.

With a bit of awkward, I see the new swap space.

Thanks

I'll know more on how this may help or not help me a bit later on.