I have trouble loading my website page where I have table with almost 70k data. In my local server it is not taking much time at all however in production it is taking few seconds to load. What can be the reason for that?

Question

I have trouble loading my website page where I have table with almost 70k data. In my local server it is not taking much time at all however in production it is taking few seconds to load. What can be the reason for that?

Nikita 0

When I am running my webapp in my local server it is not taking time at all. But when I run same webapp in production it is taking few seconds time to load data. I have my webapp built on django framwork.

adwaid krishna 0 Reputation points

2025-05-02T05:58:24.1266667+00:00
sounds like a classic "runs fast on my machine but chokes on prod" situation. i've been there. so here's what might be going on:

local db vs prod db: on your local setup, the db might be running super fast (sqlite maybe?) and the network is basically 0 latency. in production, you're probably using something like postgres or mysql and depending on where it's hosted, even a small network delay adds up, especially with 70k rows.

server specs: your local machine might actually be beefier than the production server (cpu, ram, etc). prod might be on shared hosting or limited resources, so it struggles a bit.

debug mode difference: django in dev mode (local) doesn't do a bunch of things prod mode does, like extra security checks, compression, etc. prod could be doing more behind the scenes.

data rendering: if you’re throwing 70k rows into an html table directly, that’s gonna lag the browser. like real bad. local browser might be fine, but prod browser might choke, especially for users on weaker devices or slow connections.

no pagination or async: if you're not paginating or using ajax to load chunks of data, it’s dumping 70k rows at once. that's a heavy trip, even if it's fast on localhost.

cdn / static files: sometimes in prod your css/js are not loading as fast due to CDN config or caching issues. makes the whole thing feel slower.

prod server config: gunicorn/uwsgi might not be tuned right, or you’re missing db indexing or query optimizations in prod. local might just be forgiving.

curious bro to curious bro, can you check:

how long the actual query takes on prod db (use django debug toolbar or logging)

if you’re using pagination or not (if not… please do)

what kind of db you’re using on prod vs local

any frontend js rendering delays in devtools network tabbrooo i feel you... sounds like a classic "runs fast on my machine but chokes on prod" situation. i've been there. so here's what might be going on:

local db vs prod db: on your local setup, the db might be running super fast (sqlite maybe?) and the network is basically 0 latency. in production, you're probably using something like postgres or mysql and depending on where it's hosted, even a small network delay adds up, especially with 70k rows.

server specs: your local machine might actually be beefier than the production server (cpu, ram, etc). prod might be on shared hosting or limited resources, so it struggles a bit.

debug mode difference: django in dev mode (local) doesn't do a bunch of things prod mode does, like extra security checks, compression, etc. prod could be doing more behind the scenes.

data rendering: if you’re throwing 70k rows into an html table directly, that’s gonna lag the browser. like real bad. local browser might be fine, but prod browser might choke, especially for users on weaker devices or slow connections.

no pagination or async: if you're not paginating or using ajax to load chunks of data, it’s dumping 70k rows at once. that's a heavy trip, even if it's fast on localhost.

cdn / static files: sometimes in prod your css/js are not loading as fast due to CDN config or caching issues. makes the whole thing feel slower.

prod server config: gunicorn/uwsgi might not be tuned right, or you’re missing db indexing or query optimizations in prod. local might just be forgiving.

curious bro to curious bro, can you check:

how long the actual query takes on prod db (use django debug toolbar or logging)

if you’re using pagination or not (if not… please do)

what kind of db you’re using on prod vs local

any frontend js rendering delays in devtools network tab
Nikita 0 Reputation points

2025-05-02T08:47:00.42+00:00
Thank you for your response.

I have tried giving time estimation expression in js from start to end of datatable execution and i am doing console.log to print time, but that shows 45ms around time and that prints even before my data is loaded in table.

I am using pagination and ajax to load data so that is not an issue.

On production i am using Azure Database for PostgreSQL flexible server. On local I am using sqlite3 database.

Only js file for datatable is taking time to load.

I am not sure what the real problem is, I have even given pagination and loading data with ajax. It only happens with pages where data is more. Is it problem of app service plan or database server?
adwaid krishna 0 Reputation points

2025-05-02T12:22:56.82+00:00
ahhh now we’re getting somewhere … thanks for laying it out clearly.

so you’re using pagination + ajax — that’s good, rules out a lot of obvious stuff. now the juicy clue is this: only the JS file for datatable is taking time to load, and it happens more on pages with more data. let’s dig this a bit like proper nerd detectives:

here’s my take:

that console.log timing you're using — it just checks how fast the JS executes, not when the actual data finishes loading via ajax and renders. datatables does async ajax under the hood, so your timer ends before data is in. to properly time it, use the datatable callback like:

js CopyEdit $('#myTable').DataTable({ ajax: 'your-url', initComplete: function () { console.log('data load complete at:', performance.now()); } });

this logs when data is actually rendered. your 45ms might just be the JS booting, not real load.

js file taking time to load — if you’re loading datatables.min.js or other dependencies from a CDN, and the browser can’t cache them properly (or the CDN is being slow in prod), that could delay things. check devtools → Network tab → check "JS" files — see if the datatables one is showing high "Waiting (TTFB)" or "Content Download" time.

app service plan — yep, it could be a bottleneck. free or low-tier Azure plans throttle CPU and I/O hard. if you’re serving static files like .js through Django instead of proper static file hosting (like Azure Blob/CDN or whitenoise), it’s slower.

Azure PostgreSQL server — maybe not the core problem here yet, because you're ajax loading paginated data — that should be fast unless the query itself is slow or db is in a slow region. BUT if your db and app are in different regions, network latency hits.

some wild but real suggestions:

check if your static files are being served from Django in production — don’t do that. use whitenoise or put them in Azure Storage or CDN.

are you using collectstatic and setting correct STATIC_ROOT, STATIC_URL, and STATICFILES_STORAGE in settings?

check if the js file is being gzipped and cached (inspect response headers like Content-Encoding, Cache-Control).

open the browser devtools → network → throttle to “Fast 3G” → reload page → check which thing is slow.

try downloading datatables js file locally and serve it yourself (not from CDN) and see if it helps. sometimes Azure-hosted apps block/slow down CDN hits due to weird firewall rules.

and yeah, it can definitely be related to the app service plan if it’s underpowered or not scaled properly. if your CPU/memory is throttling, even loading JS files can lag like molasses.

so , next move:

profile the js file load time

log ajax load finish with that initComplete

test same in local prod-like build (sqlite + static files served same as prod) and compare

Your answer

Nikita 0 Reputation points

2025-05-02T08:47:00.42+00:00

Thank you for your response.

I have tried giving time estimation expression in js from start to end of datatable execution and i am doing console.log to print time, but that shows 45ms around time and that prints even before my data is loaded in table.

I am using pagination and ajax to load data so that is not an issue.

On production i am using Azure Database for PostgreSQL flexible server. On local I am using sqlite3 database.

Only js file for datatable is taking time to load.

I am not sure what the real problem is, I have even given pagination and loading data with ajax. It only happens with pages where data is more. Is it problem of app service plan or database server?

Share via

I have trouble loading my website page where I have table with almost 70k data. In my local server it is not taking much time at all however in production it is taking few seconds to load. What can be the reason for that?

Your answer