No longer needed in v16. A compact will reorganize the data file, and then do a complete reindex.
We do our compacts on 4D Server 64-bit on Windows. We do it on a machine that has enough RAM so that the cache never gets used up. Since version 16 and the latest new-and-improved cache manager on Windows, there's a huge performance problem when 4D has to release memory from the cache. Another approach we took once when we didn't have enough RAM on the compacting machine to prevent a cache purge, since it was a very fast SSD we set the cache size to be far higher than the installed memory. This forced some paging at the end of the process, but this was far faster on an SSD than letting 4D try to slowly release memory. You might have better luck on a late R-release in v15, which has the old cache manager. Or on a Mac. > On Jul 26, 2018, at 11:31 AM, Chip Scheide via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I have not had to do this, but I remember seeing others mention this > process. > > it went something like this: > - TURN OFF the indexes through out the database. > - let compact do its job > - TURN ON indexes through out the database > - let database index > > -- not sure if this is needed/helps but you might want to look at > turning off triggers too. > Chip ********************************************************************** 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 **********************************************************************
