# Collaborate on Optimizing a new Custom Rule **URL:** \ **Category:** Development\ **Tags:** new\_filter\_rules, performance\ **Created:** [December 10, 2022, 5:59pm UTC](https://gramps.discourse.group/t/collaborate-on-optimizing-a-new-custom-rule/3063 "2022-12-10T17:59:41Z")\ **Posts on this page:** 1\ **Showing post:** 26
**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\ **Post date:** [March 15, 2025, 2:08pm UTC](https://gramps.discourse.group/t/collaborate-on-optimizing-a-new-custom-rule/3063/26 "2025-03-15T14:08:30Z")
> [@dsblank](#): > > As to how to make Gramps faster with filters is a different question. It may be time to revisit that issue 🙂 Revisited as part of the Gramps 6.0 enhancements. See > [@What to expect (and test) with Gramps 6.0 beta](https://gramps.discourse.group/t/what-to-expect-and-test-with-gramps-6-0-beta/6989): > > As noted, Gramps 6.0 comes with a host of changes all over the app—from the UI, help links, and items under the hood. I’m especially interested in getting feedback on three items: Upgrading Any errors throughout reports or UI views Performance of your filters (1) The upgrade path is a little bit unique from past upgrades. Because the system has to read in your old data (so-called “pickled” arrays, aka “blobs”) but then write out the new internal format (JSON data), we’ve created an abstracti… --- _[View the full topic](https://gramps.discourse.group/t/collaborate-on-optimizing-a-new-custom-rule/3063)._