[JBoss JIRA] (FORGE-2460) support an easy way to eagerly load commands
by James Strachan (JIRA)
[ https://issues.jboss.org/browse/FORGE-2460?page=com.atlassian.jira.plugin... ]
James Strachan commented on FORGE-2460:
---------------------------------------
haven't had a chance to profile; for project-new its probably the archetype stuff; my current bottleneck does use mvn facets mind you
> support an easy way to eagerly load commands
> --------------------------------------------
>
> Key: FORGE-2460
> URL: https://issues.jboss.org/browse/FORGE-2460
> Project: Forge
> Issue Type: Feature Request
> Reporter: James Strachan
>
> It can take a little while for JBoss Forge to load commands. When using JBoss Forge on the server side it'd be great to just load all the commands into memory upfront so that if someone tries to use a command the web app is very responsive and doesn't hang for a few seconds.
> Right now I've been adding a few hacks to preload a few commands by hand by issuing dummy commands to validate commands to force them to activate and classload etc.
> I wonder is there a way we could do this generically?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 3 months
[JBoss JIRA] (FORGE-2460) support an easy way to eagerly load commands
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2460?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-2460:
----------------------------------------
Interesting.
Have you had a chance to profile to see where the bottleneck is? Last time I checked, it was the Maven integration's fault (It is a bit slow when accessed the first time).
> support an easy way to eagerly load commands
> --------------------------------------------
>
> Key: FORGE-2460
> URL: https://issues.jboss.org/browse/FORGE-2460
> Project: Forge
> Issue Type: Feature Request
> Reporter: James Strachan
>
> It can take a little while for JBoss Forge to load commands. When using JBoss Forge on the server side it'd be great to just load all the commands into memory upfront so that if someone tries to use a command the web app is very responsive and doesn't hang for a few seconds.
> Right now I've been adding a few hacks to preload a few commands by hand by issuing dummy commands to validate commands to force them to activate and classload etc.
> I wonder is there a way we could do this generically?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 3 months
[JBoss JIRA] (FORGE-2460) support an easy way to eagerly load commands
by James Strachan (JIRA)
[ https://issues.jboss.org/browse/FORGE-2460?page=com.atlassian.jira.plugin... ]
James Strachan commented on FORGE-2460:
---------------------------------------
This is what I'm doing now btw
https://github.com/jstrachan/fabric8/blob/cdelivery/forge/fabric8-forge-c...
part of the issue could maybe be to do with multi-step wizards; maybe that might help; if there's a way to force all the steps for all commands to be eagerly loaded? Currently DevOpsEdit is really slow too on startup which is basically a few wizard steps
> support an easy way to eagerly load commands
> --------------------------------------------
>
> Key: FORGE-2460
> URL: https://issues.jboss.org/browse/FORGE-2460
> Project: Forge
> Issue Type: Feature Request
> Reporter: James Strachan
>
> It can take a little while for JBoss Forge to load commands. When using JBoss Forge on the server side it'd be great to just load all the commands into memory upfront so that if someone tries to use a command the web app is very responsive and doesn't hang for a few seconds.
> Right now I've been adding a few hacks to preload a few commands by hand by issuing dummy commands to validate commands to force them to activate and classload etc.
> I wonder is there a way we could do this generically?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 3 months
[JBoss JIRA] (FORGE-2460) support an easy way to eagerly load commands
by James Strachan (JIRA)
[ https://issues.jboss.org/browse/FORGE-2460?page=com.atlassian.jira.plugin... ]
James Strachan commented on FORGE-2460:
---------------------------------------
Yeah - it still takes a while to 'really warm up' (e.g. for the New Project to load the archetypes and so forth. I found the only real way really warm it up (so that the first execution isn't really slow) is to try execute/validate each command.
> support an easy way to eagerly load commands
> --------------------------------------------
>
> Key: FORGE-2460
> URL: https://issues.jboss.org/browse/FORGE-2460
> Project: Forge
> Issue Type: Feature Request
> Reporter: James Strachan
>
> It can take a little while for JBoss Forge to load commands. When using JBoss Forge on the server side it'd be great to just load all the commands into memory upfront so that if someone tries to use a command the web app is very responsive and doesn't hang for a few seconds.
> Right now I've been adding a few hacks to preload a few commands by hand by issuing dummy commands to validate commands to force them to activate and classload etc.
> I wonder is there a way we could do this generically?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 3 months
[JBoss JIRA] (FORGE-2460) support an easy way to eagerly load commands
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2460?page=com.atlassian.jira.plugin... ]
George Gastaldi commented on FORGE-2460:
----------------------------------------
Have you tried calling {{org.jboss.forge.addon.ui.command.CommandFactory.getCommands()}} when the server starts? You need to lookup {{CommandFactory}} through the {{AddonRegistry}}.
> support an easy way to eagerly load commands
> --------------------------------------------
>
> Key: FORGE-2460
> URL: https://issues.jboss.org/browse/FORGE-2460
> Project: Forge
> Issue Type: Feature Request
> Reporter: James Strachan
>
> It can take a little while for JBoss Forge to load commands. When using JBoss Forge on the server side it'd be great to just load all the commands into memory upfront so that if someone tries to use a command the web app is very responsive and doesn't hang for a few seconds.
> Right now I've been adding a few hacks to preload a few commands by hand by issuing dummy commands to validate commands to force them to activate and classload etc.
> I wonder is there a way we could do this generically?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 3 months
[JBoss JIRA] (FORGE-2460) support an easy way to eagerly load commands
by James Strachan (JIRA)
James Strachan created FORGE-2460:
-------------------------------------
Summary: support an easy way to eagerly load commands
Key: FORGE-2460
URL: https://issues.jboss.org/browse/FORGE-2460
Project: Forge
Issue Type: Feature Request
Reporter: James Strachan
It can take a little while for JBoss Forge to load commands. When using JBoss Forge on the server side it'd be great to just load all the commands into memory upfront so that if someone tries to use a command the web app is very responsive and doesn't hang for a few seconds.
Right now I've been adding a few hacks to preload a few commands by hand by issuing dummy commands to validate commands to force them to activate and classload etc.
I wonder is there a way we could do this generically?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 3 months
[JBoss JIRA] (FORGE-2459) ShellTest implementation should not be a singleton
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-2459?page=com.atlassian.jira.plugin... ]
George Gastaldi closed FORGE-2459.
----------------------------------
Resolution: Done
> ShellTest implementation should not be a singleton
> --------------------------------------------------
>
> Key: FORGE-2459
> URL: https://issues.jboss.org/browse/FORGE-2459
> Project: Forge
> Issue Type: Enhancement
> Components: Test Harness
> Affects Versions: 2.18.0.Final
> Reporter: George Gastaldi
> Assignee: George Gastaldi
> Fix For: 2.18.1.Final
>
>
> ShellTest shouldn't be a singleton, since the output impacts on individual tests in the same test class, therefore producing errors while running tests in different environments where the test order changes.
> It should also be {{AutoCloseable}} to support releasing resources when needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 3 months
[JBoss JIRA] (FORGE-2459) ShellTest implementation should not be a singleton
by George Gastaldi (JIRA)
George Gastaldi created FORGE-2459:
--------------------------------------
Summary: ShellTest implementation should not be a singleton
Key: FORGE-2459
URL: https://issues.jboss.org/browse/FORGE-2459
Project: Forge
Issue Type: Enhancement
Components: Test Harness
Affects Versions: 2.18.0.Final
Reporter: George Gastaldi
Assignee: George Gastaldi
Fix For: 2.18.1.Final
ShellTest shouldn't be a singleton, since the output impacts on individual tests in the same test class, therefore producing errors while running tests in different environments where the test order changes.
It should also be {{AutoCloseable}} to support releasing resources when needed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
9 years, 3 months