Difficulty in uploading datasets

Hello Community,

I am facing difficulties in uploading datasets on HEAVY for the last 24 hours.

Smaller datasets (in kbs) are uploaded, but relatively larger datasets (in the range of >5 mbs) are throwing a ‘Request Entity Too Large Error’ (Screenshot of the error attached). In the past, datasets much larger than this were easily uploaded on HEAVY, this is only a recent issue.

In addition to this, dashboards are extremely slow to load. Is anyone facing a similar issue? Guidance on any resolution to these issues would be highly appreciated.

Lastly, does HEAVY have a helpdesk E-mail to which I can reach out?

Error Page 1

The file uploaded in the above screenshot is the ZIP of shape files.

Thanks in advance!

Hi @Prakhar_123,

About the upload problem
Heavy immerse isn’t using any webserver except the proprietary one, so the error message “413 Request Entity Too Large” is coming from somewhere else; probably a proxy using Nginx/1.21.6.
Maybe recently, your organization has changed the proxy server or the configuration of the proxy itself?
I loaded a 200MB large ShapeFile into Heavy Immerse using the local plan without any issue.
I suggest checking with your IT department if something has happened lately.

About the slowdown.
If the slowdown happens immediately after a server startup, you will likely face a slow disk issue because the server must load all the data your dashboard needs from disks to memory.

But if it’s happening every time you close and then re-open a browser, it probably is a network issue and possibly related to the first one.

To determine if you have access from the browser only, you can figure out what’s causing the slow down of dashboards in two ways.

First, open the dev-tool of your browser by pressing F12, go to the Network session, and sort for the time.

For example, I have some calls taking over 150ms that could lead to a slow response time.
Clicking on it and selecting Timing I get some info about which part of that call takes so much time

In this case, you waited for the response from the server without any significant enqueuing or transfer time.

To know what is going on, select Payload and check the contents.

Unsurprisingly is a render vega call that’s taking so much time.

If you have an account with administrative rights, open a SQL editor on another tab (right-click and open in a new tab) and run those commands.

alter system clear CPU memory;
alter system clear GPU memory;

Then come back to your dashboard to check if it’s taking a long time to reload the data.

If you are using the Free version of the product, you can get assistance here in the community forum, or thru Intercomm. With an Enterprise subscription, you can get support on different channels.

I hope this helps, let me know if you have any more doubt or we can help you more.