Sire, you sound all smart and ish *swoon*
Thank you Baby!
Sire, you sound all smart and ish *swoon*
This past Saturday I upgraded the vBCommerce software to the latest version. Later that evening the server began experiencing high loads that made it difficult to access the site. ...
I know vBCommerce has become pretty popular on this board and I will do all I can to save it. Please be patient while I investigate all of the options that are available.
ok...im gonna need you 2 to get a room....all this insider talk is going to make my head explode.....
Condi, I will be patient. Thanks for the explanation. I'm probably in the minority when I say I could careless about vBCommerce, but that's just me. It's more important for me to be able to get my LSA fix daily...especially when things are really hopping. The other night was almost the worst night in forever (yeah, I'm being dramatic). I could not get on LSA for like 24 hrs. and when I was able to get on it kept going down. :disapointed: Humph! I was just :at-wits-end: and frustrated, so much so that I tried going to another site. :bulgy-eyes: Oh Condi, it was absolutely awful! : I absolutely hated it. If it ever comes down to vBCommerce and LSA going down, I say bunk vBCommerce! crying: Sorry y'all, but I've been traumatized beyond explanation. *sniff sniff*
the word is "quiet"...and i can tell her to get a room....she doesn't usually scare me....man..shhhhushh!! If yall would be quite & read : 4 a moment instead of gossiping you may learn a little something about the state & condition of the board.
Eta: I personally think it's rude 2 ask condi 2 "get a rm" on her own site. You *fail* hard 4 that one!!
the word is "quiet"...and i can tell her to get a room....she doesn't usually scare me....
I normally don't let this boards liars and bullshitters get to me but after sleeping for about 7 hours over a 72 hour period while I debugged this board I'm not going to tolerate it in this thread. I know the lie that's going around is that the board was hacked. It wasn't. And if you want to spread that lie, take it somewhere else.
ok...im gonna need you 2 to get a room....all this insider talk is going to make my head explode.....
Sounds like a memory leak in the latest version of vBCommerce. Obviously, I have not seen the server statistics but if there is a process server side that continually spins and consumes more and more resources the issue sounds like the vb commerce plug in as you have undoubtedly identified. Unless we can distribute that load across multiple dedicated processors or machines(load balance) and place a resource limit on the process causing the issue I can't think of any other option off the top of my head. But even doing that is crutching up a badly written piece of software that shouldn't be causing our issues in the first place.
Alternatively, I think many of the shop owners MAY be willing to copy their items locally, downgrade the vbcommerce plug-in to the working version, and set up the shops again in the old version.
Just a thought from the outside looking in.
I agree with you in your conclusion as it doesn't sound as if it warrants a physical hardware solution. Also, I don't think its necessary to change your storage solution either. Your initial cost and support cost would also increase moving to a RAID solution so would your management time. The configuration of your RAID environment would also take considerable time. I think our best case scenario in this case is to back out the current implementation of VBCommerce and re-install the previous version. We could give the shop owners, say 2 days to copy all of their .gifs, folders, and price points locally and remove this beta version of vbcommerce. We then re-install the previous version, ensure working functionality, then allow all of the shop owners back in to upload their .gifs etc.
This way, it takes the burden off of the server and your time while giving the LSA users back the functionality of vbcommerce while at the same time eliminating those who do not want shops any longer or who are now not committed to the idea of owning a shop.
Otherwise, we continue on without vbcommerce unless we find someway to spread the load across dedicated processors or machines in order to support the spiraling memory usage which still may bring down both servers at a later time anyway. The issue would still apply when the 'gold' release is available as we have no assurance that this issue will be corrected nor do we have a confirmed delivery date of said solution. It doesn't sound like the developer applies any rigor in the QA process so we are still in the dark employing blind hope.
Going forward, we may utilize a separate logical environment where we do these installations in a 'non-production' environment(call it test or patch-test) which mirrors LSA and which may be kept current on a weekly basis. This way we can do these types of installations and test all aspects of the plug-in before releasing it to the production environment. I don't know how expensive another logical environment would be for you but we could trap these types of issues before rolling them to PROD.
Just my initial thoughts
: Umm Sire who are you, really???? Some CFO computer geek intellectual black nationalist dude: