perhaps the reindexing of the 250k table has saturated the cache, leaving little space the smaller table.
FLUSH CACHE (FLUSH BUFFERS) with the * could be used to purge objects from the cache, if that's the case. also 15R4 improved the indexing process https://download.4d.com/Documents/Products_Documentation/LastVersions/Line_15R4/VIntl/4D_Upgrade_v15_R4.pdf before the optimisation, 4D could jump from table to table during indexing. > 2019/06/27 10:04、JOHN BAUGHMAN via 4D_Tech <4d_tech@lists.4d.com>のメール: > Is this normal? Is there anything I can do to speed them up short of > unindexing some of them? Are different indexing methods faster than others? ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
