New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
I'm using the latest version, and I haven't had any problems. I'm not using SSD servers, though I doubt that would effect the stability of Proxmox.
This node is a production node and has no problems and or issues at all with performance and stability.
Is it the 250gb ssd?
I run latest version, I think the issue may be with the config rather than the servers themselves.
All versions stable for me...
I've used all versions from 1.5 up to current with various configs on Squeeze and Wheezy and never had any stability issues.
42
So do I.
I go hole way up 3.1 3.3-5... on a supermicro chassis, ecc ram... hypervisor is dam stable... never got an issue with it, got some stability problem inside one of the VM-s but that is not related to proxmox but to guest os...
PS I'm curious in do anyone here use enterprise repo ?
This was revised by Deep Thought some time ago. It's 43 now, there has been a rounding error after a nasty division by cucumber.
Nein, It's Lewis Hamilton!
Doch! Hamilton was 44.
back to topic: there is nothing called as "stable proxmox version" 3.x is the current branch and you must use it anyway.
there is a bug I ran into when installing proxmox 3.2 and 3.3 into haswell motherboards of some kind.After installation system stucks at black screen and does not boot, but it can also be fixed by installing 3.1 and upgrading it later.
Proxmox " deb http://download.proxmox.com/debian wheezy pve-no-subscription " repo is very stable for me for the whole 50 or so proxmox boxes...
Strange, I must be lucky as I never encountered this.
What are the status of your SSDs? What does the health data on them look like? Are they dying?
they are not dying.... i open 30 JingLing VPS on 1 SSD+Memory Cache and got so slow, but some buddy running SolusVM is running 50 on same spec
LOL, that probably is destroying your SSD quite happily. Depending on the quality/specification of your SSD and controller will determine the IOPS that you can expect. Your friend's server probably has a higher spec SSD and controller.
it's 80000IOps isn't that enough?
Thats your issue buddy.
You need to study the REAL performance, not something off a marketing sheet.
I remember you you are the guy with 25 vps-es on one node not getting 25 times resources (or something similar) scam - drama thread form September around the time i register here, glad you listen to the LET advice get a dedi and virtualize it...
I'm not completely sure in my first statement cause I use Solus only for evaluation 15 days (it didn't fit my purposes) - think i read that it by default setup file system to work in writeback mode, Proxmox do not do that... but you can do it yourself hope you setup it with ext4 http://blog.smartlogicsolutions.com/2009/06/04/mount-options-to-improve-ext4-file-system-performance/
does your buddy has different setup on guests? ... I read here that this jinglinging thing is writing hard in temp folder so you can mount temp in ram...
Yeah some do that, although it would be better to just not run Jingling in the first place.
yes, temp is mounted...
then ask your buddy to check for the writeback and check how it is setup on your Proxmox