[OSRM-talk] OSRM-talk Digest, Vol 46, Issue 18

Mark Hagers mark at marksman-do.nl
Tue Nov 1 12:18:36 UTC 2016

Hi all,

Since my last post I have been experimenting a bit more and on a different win box so far with promising results:

To begin with I put everything in a single folder (not necessary on OSX, but apparently it is on Win). This time the settings in .stxxl.txt are used and the swap file is created where expected.
Processing osrm-extract does work and so far without out-of memory errors.
I expect this to take quite a bit of time if everything works as planned.
I'll update when it's done.

best regards


> On 1 nov. 2016, at 10:58, Mark Hagers <mark at marksman-do.nl> wrote:
> Hi Surya,
> Thanks for your response.
>> On 31 okt. 2016, at 19:47, osrm-talk-request at openstreetmap.org <mailto:osrm-talk-request at openstreetmap.org> wrote:
>> Message: 4
>> Date: Mon, 31 Oct 2016 14:47:17 -0400
>> From: Surya Suluh <surya at productivityapex.com <mailto:surya at productivityapex.com>>
>> To: Mailing list to discuss Project OSRM <osrm-talk at openstreetmap.org <mailto:osrm-talk at openstreetmap.org>>
>> Subject: Re: [OSRM-talk] Running on windows
>> Message-ID:
>> 	<CAFsB90EoXtvnfvZEb3agc7RGzavBhXD0tEA5OED87GKsM=c6kw at mail.gmail.com <mailto:CAFsB90EoXtvnfvZEb3agc7RGzavBhXD0tEA5OED87GKsM=c6kw at mail.gmail.com>>
>> Content-Type: text/plain; charset="utf-8"
>> Mark,
>> I was able to process and run netherland latest using latest build on my
>> windows box (Windows 10 build 14393.351).  Only thing I can recommend is to
>> make sure:
>> 1. You have vc++ 2015 redist update 3 install.
> is installed
>> 2. You have c:\temp\ directory.  (This is the default of .stxxl.txt, you
>> can change this to whatever folder you want by editing that file.)
> I have this setup:
> d:\osrm\
> 	.stxxl
> 	...
> 	(contents of the osrm_Release.zip file are unpacked into this dir)
> d:\osrm-data\
> 	netherlands-latest.osm.pbf
> d:\temp\stxxl\
> 	(empty)
> I edited the file .stxxl.txt contents to this:
> 	disk=d:\temp\stxxl,10000,wincall
>> 3. Run osrm-extract.exe -p car.lua netherland-latest.osm.pbf
> I open a command line (a regular windows cmd window) on d:\osrm-data\:
> When I run this from the cmd:
> ..\osrm\osrm-extract.exe -p ..\osrm\foot.lua .\netherlands-latest.osm.pbf
> It starts processing with the following output:
> [info] Using script ..\osrm\foot.lua←[0m
> [info] Input file: netherlands-latest.osm.pbf←[0m
> [info] Profile: foot.lua←[0m
> [info] Threads: 4←[0m
> [STXXL-MSG] STXXL v1.4.99 (prerelease/Release) (git 78dd7ec6e72d7d6ef1209e594fc08e3759af5099) + gnu parallel(__GLIBCXX__)
> [STXXL-ERRMSG] Warning: no config file found.
> [STXXL-ERRMSG] Using default disk configuration.
> [STXXL-MSG] Disk 'C:\Users\mark\AppData\Local\Temp\6\stxxl.tmp' is allocated, space: 1000 MiB, I/O implementation: wincall delete_on_exit queue=0 devid=0
> [info] Parsing in progress..←[0m
> [info] input file generated by Osmium (http://wiki.openstreetmap.org/wiki/Osmium <http://wiki.openstreetmap.org/wiki/Osmium>)←[0m
> [info] timestamp: 2016-10-31T20:28:03Z←[0m
> After the above it logs out of memory errors repeatedly.
> As you can see in the output, the .stxxl file is apparently not read by STXXL.
> The configured dir remains empty, but the temp file seems to be created on disk c (the default?) which has insufficient disk space, no doubt causing the out of memory issues.
>> 4. Run osrm-contract.exe netherland-latest.osrm
>> 5. Run osrm-routed.exe netherland-latest.osrm
> Never got that far yet.
> •	What do I need to do to let STXXL obey the .stxxl config file? 
> •	Does it need to be in a different location?
> •	Is there a command line parameter to have this file read properly?
> •	Do I need to rearrange the locations of the other files?
> Thanks for your help!
> best regards,
> Mark Hagers <mark at marksman-do.nl <mailto:mark at marksman-do.nl>>

Mark Hagers
mark at marksman-do.nl
twitter: @markchagers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osrm-talk/attachments/20161101/23417cf7/attachment-0001.html>

More information about the OSRM-talk mailing list