Page 1 of 2
Pesistant Storage - Interim Solutions
Posted: Sat Jun 06, 2009 1:30 am
by NickD
Persistant Storage appears to be working in BG. Therefore I surmise that the reason p-storage in TSM is causing crashing is because TSM has so much of it in use.
1. Would it be possible to selectively clear out p-chests that are no longer in use/owned by dead PCs? Perhaps even clear them all out completely, just so they can be used again. They'd probably all get wiped with the DB solution anyway.
2. Another temporary solution to the problem in terms of PC death would be to make the body non-persistant storage. This means you'd have to carry the body and items separately and it'd all get wiped when the server resets, but it's better than causing crashes whenever someone dies or tries to loot a dead body.
I would suggest looking into implementing 2 above anyway. And after implementing the DB solution for p-storage, convert the body to p-storage object when they log out, rather than what is most likely to be the middle of combat.
Re: Pesistant Storage - Interim Solutions
Posted: Sat Jun 06, 2009 5:30 am
by Brother Humphrey
If the first suggestion is the one to be implemented, I'm sure all of us players would appreciate a time period where we could empty our PChests with DM supervision and then store them on a DM avatar so we wouldn't get slowed to a crawl with an extra 300+lbs of gear we have no current need of, but can't get rid of due to needing it for future events.
That said, I would ask AL to search the DB from the time after Knut Horther's death in order to determine what disappeared from Sword Eliisabet Fayth Trueblade's pchest in H.I..
Re: Pesistant Storage - Interim Solutions
Posted: Sat Jun 06, 2009 1:00 pm
by Riotnrrd
I offer support for prioritization of pstorage in TSM.
I am willing to assist as possible.
Re: Pesistant Storage - Interim Solutions
Posted: Sat Jun 06, 2009 7:46 pm
by Wynna
FYI, AL's out of town this weekend. Thanks for the suggestions. I'm sure he'll respond after some deserved time off.
Re: Pesistant Storage - Interim Solutions
Posted: Sat Jun 06, 2009 7:49 pm
by NickD
The top solution isn't something for AL to take care of. It's up to the DM team, cleaning up excess storage in the hope of buying AL some more time to implement p-storage.
Re: Pesistant Storage - Interim Solutions
Posted: Sat Jun 06, 2009 7:56 pm
by Wynna
There's actually very little p-storage on TSM: House Invincible, the Uni, Rhyester's Matins, ...am I missing anything? All the Uni rooms are cleaned out at PC death; I think I've taken care of the H.I. rooms a month or so ago. I can check Rhyster's.
Re: Pesistant Storage - Interim Solutions
Posted: Sat Jun 06, 2009 8:08 pm
by NickD
It might be that the storage that is there is too full or something, but if NWN2 can't handle a small amount of pstorage then that's just a bit lame.
Or I could be wrong about the cause.
Re: Pesistant Storage - Interim Solutions
Posted: Sat Jun 06, 2009 8:32 pm
by Curmudgeon
According to my probably incomplete understanding of AL's explanation, the p-storage issue is due to a problem with the NWN2 database system that came with the game (a rather clunky system built by Bioware and imported wholesale into NWN2) having problems writing to a fairly remote storage vault. You may recall that TSM's p-storage issues were minimal until we connected to the Remote Vault immediately preceding BG going Live. TA and IA have been working on a possible fix for this, but there have been some technical issues with the initial proposed fix.
An alternate fix may be possible, but it would require migrating the functions of the built-in database to an alternate scheme - it would perhaps help if we had an ALFA member who has some skills with MySQL who could step forward and offer to assist our overworked Tech Team.
BTW, the reason BG has so few issues with p-storage is that the module server is geographically and latency-wise very close to the db server.
If I understand all this right, I am afraid that emptying the currently used pchests will not have any effect on the problem.
Re: Pesistant Storage - Interim Solutions
Posted: Sat Jun 06, 2009 8:54 pm
by NickD
Ah. Well then...
I don't have experience with MySQL, but I do have a fair bit of database experience. I offered some advice in that regard at the start of the trouble, but haven't heard anything recently.
Re: Pesistant Storage - Interim Solutions
Posted: Sun Jun 07, 2009 5:50 am
by danielmn
Tower of Balance should have P-storage as well.
Re: Pesistant Storage - Interim Solutions
Posted: Tue Jun 09, 2009 2:18 pm
by AcadiusLost
Erg, lots to clarify here:
Persistent storage currently uses the (lousy, buggy) "campaign database" system that shipped with NWN1, and was left as it's same buggy self in the NWN2 game code. It was never really meant to manage the sorts of things we use it for.
The native campaign DB is stored in the /database folder of the server hosting computer, so it's not sensitive to latency between the host machine and the SQL server. If/when we move to SQL-object-based p-storage (currently the most promising route, implementation incomplete), this will become a factor.
Number of storage objects does not appear to be the determinate in this case. I've tried experimentally deleting all but a handful of storage object records, and the problem persists. (Also, recall that PC corpses are p-storage objects, so TSM has had many hundreds of them over the 14 months of Live in addition to those toolsetted).
The issue is more likely tied to the memory footprint of the server itself; TSM tends to fill about 1.6 gigabytes of server memory all by it's lonesome. When the campaign database functions are invoked for a "write" (closing a p-chest after modifying the contents), the server process may be trying to allocate more RAM for it's (highly inefficient) operations, and running into hard limitations, causing the server crash.
We could "disable" p-chests themselves centrally, so they appear empty and would not attempt to save contents (but the contents would be saved for when things are working again), but it's troublesome (would mean making a special version of our script hak for TSM, and making sure that copy was in place each time the mod is recompiled) and would still give us problems with the death system, since PC inventory might be lost OnDeath without the system there to hold on to it. For a while at least, the gear was staying with the PC in the fugue plane when the DB failed. Now, I'm not so sure.
I know it's a pain, but so is the workaround. I'd feel better sinking the time into the SQL-based reimplementation than into interim fixes. Realistically though, the SQL-based storage isn't going to be done until late June at the earliest, given my travel plans.
Your patience is appreciated.
Re: Pesistant Storage - Interim Solutions
Posted: Tue Jun 09, 2009 6:51 pm
by Brother Humphrey
We've waited this long, pal, we can wait some more. Even having given us an ETA is an improvement on the mushroom method. Thanks for all your time and effort on behalf of all of us incompetent slobs (and the rest of you competent types) who would otherwise just continue doing what we can to insure that we don't crash the server by getting themselves killed.
*Doles out patience to those in short supply*
Re: Pesistant Storage - Interim Solutions
Posted: Wed Jun 10, 2009 2:07 pm
by AcadiusLost
Had an inspiration on this last night, too soon to say for sure, but that patience might not have to be very much longer at all...

Re: Pesistant Storage - Interim Solutions
Posted: Wed Jun 10, 2009 3:49 pm
by Kest
AL is a marvel to behold in action
even when im afk most of the time
Re: Pesistant Storage - Interim Solutions
Posted: Wed Jun 10, 2009 9:20 pm
by Brother Humphrey