# Frontend Performance - 500 data fields singleton

**URL:** <https://discourse.getcockpit.com/t/frontend-performance-500-data-fields-singleton/1753>\
**Category:** General\
**Created:** [December 22, 2020, 11:52am UTC](https://discourse.getcockpit.com/t/frontend-performance-500-data-fields-singleton/1753 "2020-12-22T11:52:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dinnerout](https://avatars.discourse-cdn.com/v4/letter/d/e5b9ba/32.png) [@dinnerout](https://discourse.getcockpit.com/u/dinnerout)\
**Post date:** [December 22, 2020, 11:52am UTC](https://discourse.getcockpit.com/t/frontend-performance-500-data-fields-singleton/1753/1 "2020-12-22T11:52:20Z")

</div>

Hi all,

currently I want to make a huge JSON editable for a customer. Best case for cockpit I thought.

I wrote a little importer, which in first instance create the singleton data structure file from the existing JSON. Works like a charm and I can edit all fields … in theory. My problems seems to be the frontend performance.

The original JSON file does have 500 datafields (yes, all single and different fields, no use of collections), which I currently all handle as simple text fields. My chrome is running for a 55sec at 100% CPU when I open the singleton form for editing.

Does anybody have any experience with such kind of larger data sets ?

cheers,  
Sebastian