This link show video about usecase: user try to split one vector layer with together.MapInfo is 17.0.4.
here are data
I to repeat this on two computers:1. Windows 7, 64-bit desktop (2011) and2. Laptop (Dell, i7, 16 GB RAM, W10).
I began this more than 4 hours ago. Not yet finished.
In W7 comp it show me "creating objects" message with blue bar appr "near the 100%".
In W10 laptop it's still "not responding" and without any progressbar.
Users, who performed this kind operations for tens and tens years say, that old ver 12 and other 32-bit ones do this operations within counted minutes.
They try with old version TABs and extended TAB, no difference.What to do?
This is real blocker.
ArcGIS or QGIS in the same comp do this below 1 hour.
This issue come common in Estonian Public sector. And this is issue. They began turn to other softwares.
All 3 my main user organizations in Estonia began report slowness when they go to ver 17. I don't test it yet, but they say that ver 12.0 is more fast.I resave data into new TAB format, remove all indexes. Not win in speed.
May be geopackage? Something else?
update.Something is wrong. I change PRO>Options>system<performance->concurency level from FULL to NONE.
Task manager shows that processor usage is down to 25% (from 80+% with "full"). But, the splitting with the same data was done with less than 1 hour.
It seems that multicore processor usage is not working properly.
Now I test with ver 2019 alpha. Seems to be the same issue.
Can engineering fix this bug for the ver 2019 first release? This is real blocker for sales.
Then, check the spatial queries too.
The are overlap query between region layers has very slow performance.
"Copy style" is very slow, too.