Stefan de Konink wrote: >>> Sorry if that wasn't clear. I meant when the API 0.6 goes live >>> and the >>> database is upgraded to the 0.6 schema then the Osmosis tasks >>> supporting >>> 0.6 data will support creating full history change files. The >>> Osmosis >>> version is currently 0.30.2, I'll release a 0.31 "official >>> release" at >>> some point. >> >> It is highly probably that we will be moving to Postgres as part of >> the >> API transition, due to problems with MySQL, so all supporting >> software >> will need to be updated, including Osmosis. More info/documentation >> coming soon. > > I suggested to Grant to actually do a benchmark instead of just > picking > the next product from the stack.
When benckmarking different database systems, don't forget to include Virtuoso. Here a TPC-D benchmark comparison (lower is better): 1. Virtuoso 5.0: 626 ms 1. Oracle 10g R2: comparible 2. PostgreSQL 8.1.6: 2063 ms 3. Mysql 5.0.27 with InnoDB: 3545 ms 4. Mysql 5.0.27: 6068 ms More test details on: http://www.openlinksw.com/dataspace/oerling/weblog/Orri%20Erling%27s%20Blog/1131 Virtuoso has a GPL edition available at sourceforge.net Mailinglists have short response times, also from the developers. ~Ceriel _______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
