Problems solved, error messages deciphered and other time saving tit bits mainly focused on Java web development with a mac.
Friday, November 26, 2010
New Mail Client for Windows
Tuesday, October 12, 2010
Lubuntu install removed Windows boot option
I bought an HP Mini 210 netbook which is a great little machine but Windows 7 Starter uses almost all of the meagre 1GB RAM for itself making everything painfully slow. After a little research I found that the Lubuntu Linux distribution claims to have the lowest memory use of any of the Debian based desktops so I'm giving it a try.
I found I had to be online with an ethernet cable to finish the install because it could not recognise the WiFi card without installing extra drivers. After updating the software with Synaptic and rebooting I found that the windows options had disappeared from the boot menu.
To get them back I needed to run:
sudo apt-get install os-probe
sudo os-probe
sudo update-grub
Now the windows options are back in the boot menu!
Wednesday, July 21, 2010
New optimisation in Twig for merged parent queries
I have just added a really nifty corner-case optimisation to Twig for merged parent queries (relation index entities) which is needed for Target Rooms location based search. Target Rooms searches a number of map blocks at the same time using async parallel queries and then merges the results together to get rid of the duplicates. You can see the blocks it chooses by adding the debug parameter:
http://www.targetrooms.com/place/montpellier?debug
See how tightly the blocks fit to the map? It chooses the blocks using a lowest-cost formula to minimize the amount of overlap and the number of blocks queried. If there is a major city just off the screen Twig may need to sort through thousands of hotels to find the best available prices and then throw them away because they are not on the map. That makes a really slow worst case that was actually quite common before this best-fit approach.
It now asks each child query which entities it wants and gets rid of duplicates before sending off a single request to the datastore for all of them. When any of the children needs more parent entities it asks this EntitySupplier for more which in turn asks all of the children again if they need any more.
It has speed up the geospatial search HUGELY! I only recently realised that the complex part of the query (searching 6 blocks of geospatial data in parallel and sorting it by price) was completing in about 50ms!!! The simple part (bulk get of the parent results) was taking between 200 and 1200ms to do 6 bulk gets. What a surprise. You can actually see in the Google App Engine Status page that some days each simple get (not even bulk get) can take like 500ms.
Now Twig combines all bulk gets for each child query into a single bulk get which has made a huge improvement.
Eclipse debug running very slow
I hit a problem developing with App Engine which took me a long time to figure out. I have been flipping between projects so didn't really notice when GAE and GWT started so run so slowly. I have also been experimenting with JRebel and messing with JVM memory parameters. Well "suddenly" every started running really really slowly and App Engine would take around 10 minutes to start up and run my 6 async parallel queries. Was it the new version of App Engine Java introducing a concurrency problem? Was it that my local datastore local_db.bin was too big - holy shit its 10MB!
After a lot of kafuffle I finally removed all break points and viola - Every thing was lightening fast again! Even though they were not being hit they somehow slowed the dev server down to a crawl. What a massive waste of time.
Wednesday, March 17, 2010
GWT Eclipse and testing with Parallels
Author name JavaDoc on Eclipse Mac
Tuesday, February 23, 2010
GWT and Google Maps - Opening an Info Window on a Marker
This works:
map.getInfoWindow().open(latLng, content);
But this:
map.getInfoWindow().open(marker, content);
throws this:
com.google.gwt.core.client.JavaScriptException: (TypeError): b is
undefined
fileName: http://maps.gstatic.com/intl/en_ALL/mapfiles/193c/maps2.api/main.js
lineNumber: 1224
By using FireBug to break on the exception I found that the maps were looking for an anchor point for the info window:
line 1224: b=a.infoWindowAnchor
So by setting an anchor point on the markers icon before using it like so:
icon.setInfoWindowAnchor(Point.newInstance(10, 10));
MarkerOptions options = MarkerOptions.newInstance(icon);
Marker marker = new Marker(latLng, options);
the info window now opens as expected.