![]() ![]() If any of your old sessions fail to load or convert, a backup will be made so we can check it out later. Your client should be a little less laggy at times, and client shutdown should be a bit faster. Everything works the same on the front end, and all your existing sessions will be converted on update. Like with subscriptions, some users are pushing multiple gigabytes of session storage total, so there is a good amount of work to save here. Furthermore, sessions that share duplicate pages (this happens all the time with session backups), can now share that stored page, saving a bunch of hard drive space too. Now, when your session has changes, only those pages that have changed will be saved, saving a ton of CPU and HDD write I/O. Like the subscriptions and network objects breakups I've done in the past year, I 'broke up' the monolithic GUI Session object this week. If you have a client with large sessions with many important things set up, make sure you have a backup done before you update! I feel good about the code, and I try to save data on various failures, but if your situation gives errors for an unforeseen reason, having the backup ready reduces headaches all around! ![]() I always encourage a backup before you update, but this week it matters more than normal. An important part of GUI Sessions is overhauled, which should save a lot of hard drive time for larger clients. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |