António Mateus
Guppy
Hello,
Since 28 November I have been in contact with jodohost because of +30 slow responses, timeouts, and whatever error messages my client has been getting in his domain. And the site is not even in production!
The problem was tracked to sql server mssql5 and remains to be solved. I can have response times of <1s or +30s. And normally starts to degenerate until the only solution is a reboot.
I contact live chat everyday, and the answer are always "problem is been solved", "senior team is working on it" etc etc etc but problems always returns, with luck, in the next day.
I really don't know what else to do. I'm tired of inventing excuses to the client and frankly I'm tired of all this problems that I really don't understand why it happens. If you have an offending database just erase it! If the server is faulty change the server! But this can't go on and a daily reboot is not a solution!
Attached are screenshots of response times!
Ticket is #EHN-35848-305
I want a definitive and quick solution to this issue. I think I have been patient enough!
Regards,
António Mateus
Since 28 November I have been in contact with jodohost because of +30 slow responses, timeouts, and whatever error messages my client has been getting in his domain. And the site is not even in production!
The problem was tracked to sql server mssql5 and remains to be solved. I can have response times of <1s or +30s. And normally starts to degenerate until the only solution is a reboot.
I contact live chat everyday, and the answer are always "problem is been solved", "senior team is working on it" etc etc etc but problems always returns, with luck, in the next day.
I really don't know what else to do. I'm tired of inventing excuses to the client and frankly I'm tired of all this problems that I really don't understand why it happens. If you have an offending database just erase it! If the server is faulty change the server! But this can't go on and a daily reboot is not a solution!
Attached are screenshots of response times!
Ticket is #EHN-35848-305
I want a definitive and quick solution to this issue. I think I have been patient enough!
Regards,
António Mateus