JBoss WindRide - automated server configuration migration

Good news! Windup does not run for 16 hours anymore... when refactoring, we omitted to sync one constant between addons... and it was a name of indexed graph DB property. As a result, windup ran 3 times slower on SSD disk and 10 times slower on HDD. ... [More]   Now I fixed that and voila - you don't have to wait 20 hours for Windup to finish your 300 MB app   So that was [WINDUP-529] Performance issue: Query requires iterating over all vertices [(ClassificationModel:classification = ...)] . Additionally, I've increased Titan database cache size to 9 % of available heap, which I experimentally ascertained to give best results with our current default heap size. But my notion is we take wrong approach for some modeling cases and we should use edges rather than indexed properties. That could give some more performance gain, and not insignificant. That's [WINDUP-532] Performance: Change storing of classification to edges instead of vertex property .   Enjoy the recovered performance and stay tuned for more [Less]

Good news! Windup does not run for 16 hours anymore... when refactoring, we omitted to sync one constant between addons... and it was a name of indexed graph DB property. As a result, windup ran 3 times slower on SSD disk and 10 times slower on HDD. ... [More]   Now I fixed that and voila - you don't have to wait 20 hours for Windup to finish your 300 MB app   So that was [WINDUP-529] Performance issue: Query requires iterating over all vertices [(ClassificationModel:classification = ...)] . Additionally, I've increased Titan database cache size to 9 % of available heap, which I experimentally ascertained to give best results with our current default heap size. But my notion is we take wrong approach for some modeling cases and we should use edges rather than indexed properties. That could give some more performance gain, and not insignificant. That's [WINDUP-532] Performance: Change storing of classification to edges instead of vertex property .   Enjoy the recovered performance and stay tuned for more [Less]

Good news!   Windup rules, when written in Java syntax (instead of XML), is now much nicer, after we did [WINDUP-409] in PR #380 @Rules( phase = ..., .... by OndraZizka .   Before, metadata were provided by callback methods. Combined with our ... [More] insisting on space-wasting formatting, each piece of metadata required 5 lines in class source.   public class SkipArchivesRules extends WindupRuleProvider {     private static final Logger log = Logging.get(SkipArchivesRules.class);     @Override     public void enhanceMetadata(Context context)     {         super.enhanceMetadata(context);         context.put(RuleMetadata.CATEGORY, "Java");     }     @Override     public List> getExecuteAfter()     {         return asClassList(IdentifyArchivesRules.class, SkipArchivesLoadConfigRules.class);     }     @Override     public List> getExecuteBefore()     {         return asClassList(DecompileArchivesRuleProvider.class);     }     @Override     public Class extends RulePhase> getPhase()     {         return Implicit.class;     } ...   Now it's just one line with annotations:   @RuleMetadata(tags = "java", after = {IdentifyArchivesRules.class, SkipArchivesLoadConfigRules.class}, before = {DecompileArchivesRuleProvider.class}, phase = DependentPhase.class) public class SkipArchivesRules extends AbstractRuleProvider {     private static final Logger log = Logging.get(SkipArchivesRules.class); ...   Isn't it great improvement? [Less]

@michallinhard Neni ta trida k nicemu, kdyz ma jen private static metody?

RT @stefanhalbfass: Learning 30 Technologies in 30 Days: A Developer Challenge https://t.co/O2wABwXZ5Y via @openshift