Built version of pwa slow

[MitchellMonaghan]

I made a PWA and it is way slower running the built version of the app than the dev version. Same api, same data, same machine the quasar build -m pwa one is drastically slower and I don't know why, its always consuming a high amount of cpu.

"quasar": "^1.15.4"
"@quasar/app": "^1.8.6"

Does anyone know what would cause this? For example simply clicking a button that shows/hides content with v-if takes 7 seconds on the prod version of the site but on dev it works instantly. I spent all day trying to investigate/track this down but I haven't been successful.

[metalsadman]

@MitchellMonaghan haven't experienced such, but you seem to be using an outdated version of @quasar/app while using a much later version of quasar. try upgrading it https://quasar.dev/quasar-cli/app-upgrade-guide

[MitchellMonaghan]

Right now we decided to host a docker container running quasar dev for demos. Preferably I can figure this out before we need to deploy to prod as running quasar in dev in prod I assume is a bad idea.

[MitchellMonaghan]

addDep is like 3.5 seconds of my 6 second operation of simply changing page content with v-if. I'm not sure if this bottle neck makes sense for dev vs prod.

[MitchellMonaghan]

This also might be part of the problem https://reside-ic.github.io/blog/handling-long-arrays-performantly-in-vue.js/
We have data sets with 5000-30,000 elements with statistical information used for calculations and these elements get rendered onto the map as well.

[MitchellMonaghan]

I often use these large data sets in computed props for calculations

[metalsadman]

that's a lot, you need to explore more ways to handle that kind of data, like freezing the object etc.. 5000 - 30000 observed object will be too heavy of a load for the ui thread. or do your calculations in a webworker. https://vueuse.org/core/useWebWorkerFn/