nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

development performance

bartr

Hi all,

I'm trying to develop some stuff against the webapp, but am having a hard time because of the time it takes to run a single test on my machine (which is 1.3Ghz cpu with 2GB RAM): loading the whole Spring context (and instantiating all the Alfresco-beans) takes somewhere between 40 and 50 seconds every time.
Am I using an underpowered machine or should I alter some spring-configuration? (I tried whether default-lazy-init='true' on the beans-element would help, but apparently it doesn't).

I'm interested to learn what your machine-specs are and how long it takes to initialize the context.

Cheers,

Bart

Find more posts tagged with

Comments

kevinr

Yes this is a known issue. Unfortuntely you are starting the entire Alfresco server each time, loading all the third party JARs etc.etc. (there are a lot - we provide a lot of features and integrations!) There are plans to separate the server into a remotable unit. So for web-client development you will only need to restart the small web application rather than the server also. For now there is not a huge amount you can do to speed it up other than use a faster machine.

For reference, my 2.13Ghz Pentium M laptop takes about 16 seconds to start the server in runtime mode and about 25 seconds in JPDA debug mode.

Thanks,

Kevin

rdanner

Yes this is a known issue. Unfortuntely you are starting the entire Alfresco server each time, loading all the third party JARs etc.etc. (there are a lot - we provide a lot of features and integrations!) There are plans to separate the server into a remotable unit. So for web-client development you will only need to restart the small web application rather than the server also. For now there is not a huge amount you can do to speed it up other than use a faster machine.

For reference, my 2.13Ghz Pentium M laptop takes about 16 seconds to start the server in runtime mode and about 25 seconds in JPDA debug mode.

Thanks,

Kevin

I can hardly wait for remote a remoted webclient / repository / consumer apps.

Are there plans to support minimal configurations on the server / repository? I suppose a lot of the features you are building in are leveraging the extension framework.