The likely reason I made the mistake about saying I could not find 'editor' within was actually based on the inverse situation. Indexing ID field = All / no matter if Unicode or English File size = 715MB Searching for the whole or a part of the UUID took 0 seconds! (I could not measure time manually => it was instantly!) For me it is not obvious what Minimal Indexing does exactly!? Especially because the search in the not indexed ID field was nearly identically fast than with a Minimal Index.!įurther clarification. Indexing ID field = Minimal / English File size = 502MB Searching for the whole or a part of the UUID took 11.5 seconds on average. Indexing ID field = Minimal / Unicode File size = 502MB Searching for all or part of the UUID took 9 seconds on average. Indexing ID field = None / English File size = 290MB Searching for the whole or a part of the UUID took on average 12 seconds. Here are the results: Indexing ID field = None / Unicode File size = 290MB Searching for the whole or a part of the UUID took on average 8.7 seconds.

All speed tests are done with this ID field and I always searched only at the beginning of the field. Hi Matt, after talking to other Filemaker developers about this yesterday and someone reporting a performance issue with Minimal Index, I did a little test today: I have a 'small' DB with only a few fields, but with 1.6 million records.

Filemaker macos