# Uibuilder ping timeout - possibly related to mySQL taking over 1 minute to get large data

**URL:** <https://discourse.nodered.org/t/uibuilder-ping-timeout-possibly-related-to-mysql-taking-over-1-minute-to-get-large-data/40445>\
**Category:** General\
**Tags:** database, uibuilder\
**Created:** [5 February 2021 15:23 UTC](https://discourse.nodered.org/t/uibuilder-ping-timeout-possibly-related-to-mysql-taking-over-1-minute-to-get-large-data/40445 "2021-02-05T15:23:54Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![GPG](https://avatars.discourse-cdn.com/v4/letter/g/f19dbf/32.png) [@GPG](https://discourse.nodered.org/u/GPG)\
**Post date:** [9 February 2021 17:10 UTC](https://discourse.nodered.org/t/uibuilder-ping-timeout-possibly-related-to-mysql-taking-over-1-minute-to-get-large-data/40445/9 "2021-02-09T17:10:49Z")

</div>

I need 40000+ rows because I'm retriving historical data for long period (i.e. 1 year) and I need to concatenate and to present them in a web page.

All values are of interest, I could do some work in mysql (I'm a little bit proficient) but algorithm isn't so easy (and not so portable in mysql) and I prefer to execute this work in PC web browser (client side) instead of embedded (server side).

In any case I couldn't reduce the amount of data: I use post-process to concatenate and associate info of different tables using algorithm, not to filter rows or execute simple calculations, so at the end the number of the rows are still big (40k).

---

_[View the full topic](https://discourse.nodered.org/t/uibuilder-ping-timeout-possibly-related-to-mysql-taking-over-1-minute-to-get-large-data/40445)._