# Dealing with large objects in the cache

**URL:** <https://community.apollographql.com/t/dealing-with-large-objects-in-the-cache/4135>\
**Category:** Client SDKs\
**Tags:** client, web\
**Created:** [July 29, 2022, 9:59am UTC](https://community.apollographql.com/t/dealing-with-large-objects-in-the-cache/4135 "2022-07-29T09:59:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lukas1994](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/lukas1994/32/2769_2.png) [@lukas1994](https://community.apollographql.com/u/lukas1994)\
**Post date:** [July 29, 2022, 9:59am UTC](https://community.apollographql.com/t/dealing-with-large-objects-in-the-cache/4135/1 "2022-07-29T09:59:45Z")

</div>

Apollo blocks the main thread for 10s when receiving large objects:

 ![image](https://us1.discourse-cdn.com/flex019/uploads/apollographql/original/2X/2/22fa57725911070c092e5f81a0ee0737fe2757f0.jpeg)

I’m not normalising these large objects:

```auto
      // Dimensions can have a large number of items. Creating a cache entry for each item
      // can cause a lot of CPU and memory usage on the client. This embeds dimension items
      // and all structures inside the item into the parent dimension's cache.
      // https://www.apollographql.com/docs/react/caching/cache-configuration/#disabling-normalization
      DimensionItem: {
        keyFields: false,
      },

      DimensionMapping: {
        keyFields: false,
      },

      DimensionItemDataSourceLink: {
        keyFields: false,
      },

      DimensionDataSourceLink: {
        keyFields: false,
      },

```

Is there anything I can do to avoid Apollo from traversing these huge objects? I already tried setting `assumeImmutableResults` but that didn’t help.

Appreciate your help!

---

<div class="post-metadata">

**Author:** ![lukas1994](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/lukas1994/32/2769_2.png) [@lukas1994](https://community.apollographql.com/u/lukas1994)\
**Post date:** [July 29, 2022, 11:27am UTC](https://community.apollographql.com/t/dealing-with-large-objects-in-the-cache/4135/2 "2022-07-29T11:27:41Z")

</div>

I also created a question a while ago on StackOverflow [Apollo client slow for large GraphQL response - Stack Overflow](https://stackoverflow.com/questions/72708641/apollo-client-slow-for-large-graphql-response)

---

<div class="post-metadata">

**Author:** ![ajwerner](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/ajwerner/32/4996_2.png) [@ajwerner](https://community.apollographql.com/u/ajwerner)\
**Post date:** [April 3, 2024, 7:34pm UTC](https://community.apollographql.com/t/dealing-with-large-objects-in-the-cache/4135/3 "2024-04-03T19:34:08Z")

</div>

Did you ever figure anything out with this? This seems related to my problem in [Slow updates with large cache](https://community.apollographql.com/t/slow-updates-with-large-cache/7356).