|
Dear Ivy Team I've profiled our app with VisualVM and it turned out that bundle.getString consumes about 15% of the time :
ResourceHandlerImpl.getLocalePrefixForLocateResource ... Any idea what is wrong here ? Best regards John |
|
joined analysis of the issues initiated. public discussion of this specific issues in question, so we freeze the thread for now. |
Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
Tags:
Asked: 02.03.2020 at 08:19
Seen: 1,427 times
Last updated: 12.03.2020 at 10:33
hard to say anything based on the given facts.
following recent Q&A entries I assume you are working on these performance analysis since several days. Improving execution behavior is a complex task - it's hard to make the right conclusions out of the recorded data. Therefore, I do not think that a discussion in the Q&A is the effective way to handle such issues. Nevertheless, we'd gladly support you in identifying performance issues within your ivy app. Please open a ticket so that we can tackle these issues together: https://support.axonivy.com/
" hard to say anything based on the given facts."
Hmm ... I would think these are hard facts. The question here is what is this ResourceBundle about. Is this something the application is providing ? Could it be that the resource has gotten just too large to be handled by Ivy ? May be indicate where the data is stored (if) ? Sorry I am possibly a lonely supporter of Ivy (one of the few) but I guess it's really your job to dig out if there is an issue with this bundle.
" I do not think that a discussion in the Q&A"
May be you are aware that different projects are doing exactly the same - to find out why their Ivy applications are slow. So this discussion might help the guys across the corridor working for another Ivy based project, if they come across the same issue.
look @John Moser we are passionate about our product. We love it's performance and how it helps hundreds of developers to provide solutions that scale even when many users are concurrently using the platform. Presumed that our platform was used in the way the Authors would recommend it. So no, we do not offer Java ecosystem support for each and every corner case. But we are willing to make your workflow app a success. My offer to help you stays intact.