Portal Home > Knowledgebase > Articles Database > WHM Split HD Resources?
WHM Split HD Resources?
| Posted by Qubicle, 09-26-2012, 03:22 PM |
| My server has a 2TB Platter, and a 240GB SSD.
Is there a (relatively) easy way (and possibly automated through WHM) to change which users home folder/databases is on the Platter VS SSD?
ie:
If I wanted to sell shared hosting on SSD at a premium, they can use that signup link and it creates it on the SSD drive vs the Platter (just an example).
Thanks in advance.
|
| Posted by RRWH, 09-26-2012, 04:56 PM |
| I am just putting this out there - but how would this help anyone?
When you consider that even for a user account that their website is most likely database driven. Essentially, all that would be on the SSD is their files for their website and their e-mail.
What about their Database? it will still be on the spinning metal, what about the logging for the web server (it all takes time) it will also be on the spinning metal drive.
To answer your question, no I do not know of any way.
The best way of course would be to set up multiple servers - 1 with SSD and 1 without.
The best usage of SSD is to set up your Server so that MySQL sits on the SSD drive - which is a fairly common hybrid implementation.
|
| Posted by TravisT-[SSS], 09-26-2012, 05:05 PM |
| Second this! You could also use it for caching as well.
|
| Posted by layer0, 09-26-2012, 05:32 PM |
| You can setup different home directories on each drive, and you should be able to setup accounts on different home directories. However, I'm not aware of a way to split the databases between both drives on a per user basis, so you'll either have to put all databases on the SSD, or all on the SATA. You can probably code some sort of hack to do this better, but that's probably not worth it.
|
| Posted by Qubicle, 09-26-2012, 07:24 PM |
| I understand what the best use is, and I also know that it's easy enough to do one with ssd and one without. I'm not sure if you understood me - or I didn't understand your response, but either way... I was essentially wanted to split some users away from others as a whole. I didn't want to store their files on the SSD and DB on SQL and or vice versa. The user would either be entirely SSD or entirely platter.
The primary reason for wondering is I have a user who has a fairly inactive site. They pay every month and never cause any problems. However - they have a ridiculously large amount of data being stored in SQL but not really being accessed. They have a very large but rarely used (anymore) Magento site that has a 3+GB DB, and multiple large forum databases. As a whole they are using about 10-15GB of SQL give or take. Considering they receive maybe ~200 unique visits per month account-wide... that would be an incredible waste of storage on the SSD.
|
Add to Favourites 
Print this Article
Also Read
VPS Issue (Views: 809)