# Rasa core memorization policy is very slow when it "launches DeLorean"

**URL:** <https://forum.rasa.com/t/rasa-core-memorization-policy-is-very-slow-when-it-launches-delorean/11619>\
**Category:** Rasa Open Source\
**Created:** [June 17, 2019, 2:28pm UTC](https://forum.rasa.com/t/rasa-core-memorization-policy-is-very-slow-when-it-launches-delorean/11619 "2019-06-17T14:28:32Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![psfr937](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/psfr937/32/2858_2.png) [@psfr937](https://forum.rasa.com/u/psfr937)\
**Post date:** [June 24, 2019, 2:34pm UTC](https://forum.rasa.com/t/rasa-core-memorization-policy-is-very-slow-when-it-launches-delorean/11619/2 "2019-06-24T14:34:48Z")

</div>

Problems solved. It is my mistake.

It is because I have not specified max\_event\_history when I define my custom tracker store.

So, when I ahve more then 10k records, the McFly update function iterates through all of them.

After I set max\_event\_history to 100, the memorization policy is much faster.

The thread below shows how to limit the tracker history size:

> [@Size of trackers in custom tracker store](http://forum.rasa.com/t/size-of-trackers-in-custom-tracker-store/4998):
>
> Hello! I’ve created a custom tracker store object to connect my bot to a centralized key/value store. That store has limits on the size of values and is also remote to my bot. When do trackers get reset or pop old information off of the conversation? Is that configurable? I’d like to ensure trackers don’t exceed my store’s limits. Also, are trackers retrieved/saved for every new user message/bot response? Since it’s remote, larger trackers could eventually impact my bot’s performance. Thanks…

---

_[View the full topic](https://forum.rasa.com/t/rasa-core-memorization-policy-is-very-slow-when-it-launches-delorean/11619)._
