It seems to all make sense now. That is quite a bit of data and a very large number of logs. My sense is that this after you purged; so it was probably much worse before that.
I bet two years ago you had far fewer logs and caches because it was much harder then with just the PQ tool to get so much data.
One cannot grow database tables in an unlimited fashion and expect to not run into resource limitations at some point. There may be ways for Clyde to do more optimizations but I suspect that what this is telling you is that you probably need to look for solutions in your use of GSAK. In other words: can you do things differently to avoid the problem you encountered. I note that you ran into this problem because you were using a temporary database and then copying some of the records to a default database. Well, one way to avoid this problem is to just use one database to begin with (this is how I do it). This also simplifies logging caches, particularly if it takes a few days or weeks to complete the logging from a trip.
I bet two years ago you had far fewer logs and caches because it was much harder then with just the PQ tool to get so much data.
One cannot grow database tables in an unlimited fashion and expect to not run into resource limitations at some point. There may be ways for Clyde to do more optimizations but I suspect that what this is telling you is that you probably need to look for solutions in your use of GSAK. In other words: can you do things differently to avoid the problem you encountered. I note that you ran into this problem because you were using a temporary database and then copying some of the records to a default database. Well, one way to avoid this problem is to just use one database to begin with (this is how I do it). This also simplifies logging caches, particularly if it takes a few days or weeks to complete the logging from a trip.
