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
Ongoing talks with ColoCrossing, but we'll most likely be removing licensing and only doing it on colocated services due to the way they did things (breach of contract.)
Well, bloody hell! That seemed to work fine, all the way to PayPal login.
We have this in the development queue. So maybe a few months to few years.
@virmach - breach of contract is a very legal statement- what did they do? An is it your interpretation of breach- or arbitrator or court? or just more ranting about cc? So they breach and the bulk of your business is still riding on their servers - I dont buy it
@Virmach Please cancel this one if you can - not crucial if you can't - I was just taking you up on the pressure testing.
Invoice #1128491
As in our interpretation. Obviously, we'd rather not discuss it much here, but to us, it's pretty clear and I'll leave it there.
So ranting yet renting more servers from them
Yeah, +1 for this months-to-years feature request...
BTW, you do know about "View => Active" filter on the left, right? It's still an extra click, and is cumbersome to do it everytime (since it doesn't remember the last selection), but still a tiny bit better than sorting probably...
It looks like a most definite crash on the next deal, unless it doesn't get any worse but we're at pretty high CPU usage of 30~ cores out 48 right now before the next sale has even launched.
WHMCS has a feature request page they seem to pay some attention to, if enough of you go there and upvote one of these being submitted.
are they full cores or LET "threads" that are partial threads
@VirMach hi,
is there any way to know the username of the SolusVM? so I can log in to the SolusVM instead go to your billing
Our new billing panel is on an Epyc 7451 (so threads, but the CPU will go all the way up to 4800% and it's currently at 3000% max.)
Client Area starting to crawl ~1 min load but has been much worse.
Add Funds Page Don't Even Open
" Error 524" - that didn't take too long to happen. :-|
(That was for a product detail request.)
Client Area (general page) recovery was good though and came back after a few minutes.
Something's better..
client area crash again
I think you'd have more joy out of more CPU power per core rather than throwing cores/threads at it, all depends on setup I guess. If you can get some decent CPUs in a cluster or offload DB it'll probably go better.
Mmm, that's why we initially went with bigger cores. But that didn't work out and this does seem to be working out better since the overall usage is technically a lower percentage.
But still not enough, I actually think this time the NVMe is the bottleneck.
Well, a little bit slow, but no error so far. Let's the hunt begin!!!
F hell, where is the next deal? does it auto refresh or do I have to do F5?
What is actually better than NVMe ? Time to RAMdisk ?
You can use the tracker which does refresh/F5 for you
Link: https://virmach.fat32.top/
Come on,next 524!
I'd really be surprised if you haven't been running from a dedicated db server, at this stage, along with a partitioned db file system. A "first port of call" for performance on large db.
Are you on MySQL or MariaDB out of interest?
Okay, we have to look into clustering. In the meantime we'll try to actually keep the website up for you guys for non flash sale purposes.
Shouldn't most of the data be in the cache though? Assuming the server has a lot of RAM.
It does auto-refresh (pulls the plan description JSON file) every 10 seconds, no need to F5 on the official page... (Also, refreshing more frequently may trigger CF checks/blocks I think, so thread carefully if you go that way)
Unfortunately not how it works. We already have the caching way too high and it just won't work great with this many people.