Our state of the art Gantt chart


Post by ninjakon »

Hello,

Just for context, we are currently using the gantt trial version with React in Typescript.

For loading and syncing data we are using the Crud Manager following this guide https://bryntum.com/docs/gantt/guide/Gantt/data/crud_manager.
During development we never had any issues and the initial load only takes a couple of seconds.
However, when we build and deploy the frontend to our dev environment the loading time jumps to >1min.
According to the browser's network tab all the data has already been loaded from our backend.
This means the backend cannot be the problem and the additional loading time must be added on while the data is being processed in the frontend.

Does the trial version have something build in to prevent being used properly after being transpiled and deployed?
If not we will have to investigate further.

Thanks in advance.


Post by mats »

Does the trial version have something build in to prevent being used properly after being transpiled and deployed?

No. The trial code is heavily obfuscated though which impacts performance a bit.

This sounds very strange. Maybe try to do a performance profile to see what's going on? If you can provide us a test case, we can also have a look.

https://www.debugbear.com/blog/devtools-performance


Post by ninjakon »

Just for context, we have deployed our code locally which causes the same issue as if it was deployed in our dev environment.

Looking at the performance tab we have found three network requests which may cause the problem.
The network transfer is fast but the resource loading time takes >2.8min.
When we run the code locally with yarn the resource loading time is only a couple of milliseconds.

We have added the fonts to our assets and removed all React components which may cause additional loading time.
However, both efforts have proven fruitless.
The attached images show the performance the mentioned requests.

Thanks for the quick reply btw.

Attachments
Screenshot 2022-09-26 at 14.26.41.png
Screenshot 2022-09-26 at 14.26.41.png (487.81 KiB) Viewed 543 times
Screenshot 2022-09-26 at 14.25.21.png
Screenshot 2022-09-26 at 14.25.21.png (477.78 KiB) Viewed 543 times
Screenshot 2022-09-26 at 14.25.11.png
Screenshot 2022-09-26 at 14.25.11.png (479.69 KiB) Viewed 543 times

Post by saki »

These loading times sound very, very weird. None of our demos, not even the big dataset demos, load this slow. Is it really fonts which are loaded this slow? Because it's only a couple of kilobytes and there's not reason why browser should load fonts for almost 3 minutes.

We would like to help you find the cause of the problem. We would need a showcase that would demonstrate the issue, that we can run, investigate and debug. The best would be the version with removed React components.


Post by ninjakon »

Yes the problem is very strange, the worst part is that it does not even happen on every reload, only sometimes.
I will try my best to create a fresh React app to showcase the problem and post it if I manage to do so.

Thank you for your efforts so far.


Post by ninjakon »

We have build and deployed with the Pro-License and according to our QA team the issue seems to be fixed.

However, please do not close this thread yet, we have two more QA sprints before we deploy on live and will keep you up to date if the issue occurs again or if the Pro-License deploy fixed it.


Post by alex.l »

Ok, glad to hear. Please keep us updated!

All the best,
Alex


Post by ninjakon »

After another round of QA we can confirm that switching to the full license has fixed the issue.

We also optimized our backend which increased the performance of this issue even further.
Importing and persisting large MS-Project files (>3MB) takes less than five seconds.

Thanks mats, saki and alex.l for your efforts!


Post Reply