LOL! its really interesting, kept me up all night, moving from 6 to 9 is not for the faint hearted lol. will post my steps and help anyone still using old versions.
I skipped about say 15 patches, I don’t see any errors anywhere yet, but will keep testing.
lol now you should learn your lesson keep up with updates, it is much easier to update to the next version than to update after skipping view versions. Also, now we can be more objective about performance not like the last topic when you were on v6.
yep yep yep, now I have to convince them to give me 6 to 8 hours to update hahahahaha, I think it will be worth it. Also let the team just look at making the reports any faster, no big deal but if possible, great, but for me, perfect, just thinking for clients, but they should also understand big data needs time to analyze and output
Again the updates were failing so I was always careful to shutdown a client and then the exercise fails. but this will be done.
Click on Edit Posting Date and Time to give the user to submit a non current invoice.
Thanks
Jay
Wouldn’t that just be because you did that with your old version? From tomorrow maybe not?
Very good idea to delete as much historical company cruft as possible.
Maybe go through V9 settings and fill in new features too?
LOL no sleep for the geek
No that will be easy… Just show them the speed difference AND BILL THEM PROPERLY for the upgrade… Who knows you might make enough to throw some cash back into core POS/Report SQL optimisation…
You should probably grab some sleep 
in practical maintenance especially with a huge client like yours, you should never operate on the live system directly. You should have a test server where you take a snapshot of the live system, and do all your updating and testing. When you are satisfied about updating and testing, then you proceed to update the live system after business hours.
I followed the entired episode and it is highly interesting that the problem is solved.Kudos to the Team and the community.It means that medium size organisations can use erpnext.So we should not fear of performance if the sql size is up to 5Gb?
Upgrade steps for anyone moving from an old version like 6 or 7
first thanks to everyone who has helped with this, motivation, code, direction, well appreciated, I wish I could pay back somehow haha
SO…
install psutil if absent or fails…
-
sudo pip install psutil
-
remove nodejs, sudo apt-get remove nodjs
-
install nodejs v6, v8
– install curl, sudo apt-get install curl
THEN…
curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash -
THEN
sudo apt-get install -y nodejs -
bench update --reset
You may have errors with new columns in doctype, add columns and proceed…
so… from frappe-bench do
bench mysql
THEN… these 2 were needed for my case… so…
ALTER TABLE tabDocType ADD COLUMN restrict_to_domain VARCHAR(40)
ALTER TABLE tabDocType ADD COLUMN in_dialog VARCHAR(40)
THEN optionally:
7. bench build
THEN
8. bench migrate, [not recommended, but I found no issues yet] skip carefully patches in apps patches.txt files found in apps/frappe/frappe/patches.txt, similar location for erpnext patches. ** The skipping proved a necessary evil, because I realized this is the reason I never got any updates to work** thanks to @H_N for this insight. So edit document, save and enter bench migrate again, update will progress.
once done, you’re ready.
depends on your data, some patches will take a while, like some invoice and inventory patches such as adjusting valuation for negative inventory, took a while due to the sheer amount of negative inventory.
haha, I am really thinking of a way; but things with clients over here can be funny, you see once you implement software with many clients in this part of the world, its your responsibility to optimize for life! or they’ll tag your system slow and inefficient… ridiculous… butI;ll do as you have said and see the outcome. thanks again.
Well… maybe no issues, this one is 1.2GB and its fine on a core i5, 8gb vm, ssd, so if it gets to 5gb and slows, throw in more power, especially processor power. innodb buffer pool size is just 256m and the system is happy. I think we are good to go with this, this is so refreshing I must say. Kudos to the team. at this pace, this will be usable for large enterprises. I also suggest the team optimize the display for all browsers, because safari on Mac doesn’t work well.
Thanks @ganas I will do just that, just that for time sake, since I have just 5 hours on that Sunday before the opening; I will take a backup and then work on the server so if the opening time meets me; I restore the old one and get another date. But I know I’ll be faster because I intend to take the patches.txt I used with the lines I already commented out (this is exactly their image I used). Drop them in the patches folders when I’m at that point, that should speed me up a lot, it will be a lot faster… do you support?
@noetico I still your setup is too fast to settle for 3 seconds. Any hope that we will get the slow logs report? Also, note that turning on slow logs will also impact performance so if it’s on in your present instance, switch off (after you analyse the slow logs sha)
@noetico: Once you are convinced the performance issues have been sorted out, would you please close this and the previous post with a solution. If you think it is appropriate, make a new post that goes: Problem-Solution and crisply document what your problem was and what the solution is.
We are transparent - we openly discuss our problems and issues. But I know people are watching us here. The performance issues is something that would have been of concern for everybody, but sifting through all these posts is something that people may not do.
Your post will help address those concerns, plus it will tell people what htey need to do if they have a problem like you did. And who knows they may request your services to help them out. I hope they do.
Thanks
Jay
1 Like
yeah I think that would work, just from now till Sunday test the hell out of your new install to make sure that commenting out those patches is not introducing errors.
Great, please close… I have a new thread started for the upgrade, will merge performance updates there
@JayRam This is also an opportunity to show people how ERPNext is evolving not just functionality wise but also performance wise. It will encourage people to keep up with the updates because many of them don’t know what goes under the hood with all the optimizations.
3 Likes