# Performance issue because of associated relationships

**URL:** <https://community.forestadmin.com/t/performance-issue-because-of-associated-relationships/1008>\
**Category:** Help me!\
**Created:** [September 22, 2020, 8:01am UTC](https://community.forestadmin.com/t/performance-issue-because-of-associated-relationships/1008 "2020-09-22T08:01:30Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![Louis-Marie](https://avatars.discourse-cdn.com/v4/letter/l/258eb7/32.png) [@Louis-Marie](https://community.forestadmin.com/u/Louis-Marie)\
**Post date:** [October 9, 2020, 7:59pm UTC](https://community.forestadmin.com/t/performance-issue-because-of-associated-relationships/1008/15 "2020-10-09T19:59:53Z")

</div>

Hi @anon34731316,

Damned!

You were right, this was due to the overridden route `router.get('/users'...`  
I am so sorry for that mistake.  
But it is due to a specificity that I coud not guess on the use of `recordsGetter.serialize` function.

I opened a new issue (please see [performance issue #1010](https://community.forestadmin.com/t/problem-with-unattended-behavior-of-the-serialization-process/1110)) to avoid mixing subjects.  
Please see it, as it is generating the issue that I described here.

Now, with the standard routes, I agree with you: the useless smart fields of associated collections are computed when accessing the records detail.

Thanks for fixing it as soon as you can.

Best.

---

_[View the full topic](https://community.forestadmin.com/t/performance-issue-because-of-associated-relationships/1008)._