Thank you Martin for the info! I saw this statement in Weld release page:
Weld is now capable of using
bytecode-scanning utilities, such as the Jandex tool, to speed up deployment. This is especially notable in extra
large deployments (e.g. 5000+ classes) where we observed up to 20% faster
deployment.
I guess this particularly related to provide ClassFileServices service in Weld integration. Is this figure for the dynamic generating index files or index files were pregenerated? I guess if generating the index files on the fly, it might be slower than prepackaged scenarios. Do you know whether the performance difference is noticeable?
Thanks Emily ================ Emily Jiang
WebSphere Application Server, MicroProfile Development Lead
AFAIK WildFly makes use of existing Jandex indexes and if not present a new one is build on the fly (for deployment and external modules) but the generated indexes are not persisted.
But in WildFly not only Weld leverages the indexes - all other annotation-based technologies should use them too.
Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU