GWT / GXT compilation slow and freezes my Windows ?

Recently I was able to run some basic GWT / GXT compilation tests to compare time efficiency between some old and new machines using Microsoft Windows. Test results wasn’t something that surprised me much but by accident I was able to find a reason that makes GWT compilation choke even modern monster desktops (6 core Phenom 3.3GHz with fast 8GB Dual RAM and top SSD II Disc)

If you are using something else then lightweight anti-virus program your GWT compilation can be much more time consuming (depending on project size and complexity average of few times longer) and even freeze your desktop for a little while.

Suggestion: use lightweight anti-virus program (like Avast AV) or change its configuration that it would skip real time scanning of your local drive (greatly improves compilation time with NOD32, Norton AV etc…)

You May Also Like

Wicket form submit not safe for redirecting to intercept page

The problem When you have a form, that anybody can see, but only logged on users can POST, you may want to redirect the user to the login page, and back to the form after login Using wicket 1.3/1.4, if you do that using redirectToInterceptPage(loginP...The problem When you have a form, that anybody can see, but only logged on users can POST, you may want to redirect the user to the login page, and back to the form after login Using wicket 1.3/1.4, if you do that using redirectToInterceptPage(loginP...

Distributed scans with HBase

HBase is by design a columnar store, that is optimized for random reads. You just ask for a row using rowId as an identifier and you get your data instantaneously. Performing a scan on part or whole table is a completely different thing. First of all, it is sequential. Meaning it is rather slow, because it doesn't use all the RegionServers at the same time. It is implemented that way to realize the contract of Scan command - which has to return results sorted by key. So, how to do this efficiently?HBase is by design a columnar store, that is optimized for random reads. You just ask for a row using rowId as an identifier and you get your data instantaneously. Performing a scan on part or whole table is a completely different thing. First of all, it is sequential. Meaning it is rather slow, because it doesn't use all the RegionServers at the same time. It is implemented that way to realize the contract of Scan command - which has to return results sorted by key. So, how to do this efficiently?