network profile
| bio | website | |
|---|---|---|
| location | Seattle, WA | |
| age | ||
| visits | member for | 2 years, 1 month |
| seen | May 8 at 23:36 | |
| stats | profile views | 9 |
|
May 18 |
comment |
PgRouting - How to clip links when reaching max costs? One option that occurs to me is to somehow split my polylines into lots of points. That gets me closer to the right answer, but seems pretty hacky, and still doesn't quite get me there. |
|
Apr 17 |
comment |
ST_Intersection slow query Simplifying the polygons a little has allowed the operation to complete in some sort of finite time. |
|
Apr 15 |
comment |
ST_Intersection slow query shared_buffers was already on, but work_mem was off. I've added 1 GB of work mem now. |
|
Apr 15 |
comment |
ST_Intersection slow query Is 910,978 huge? This is the nice thing about starting on a new tech--I have no normative expectations :-) |
|
Apr 15 |
comment |
ST_Intersection slow query Thank you, that sounds like good advice. Some of the Windows issues such as the fork() penalty shouldn't be an issue here because I'm running a single connection, right? Also, have run VACUUM ANALYZE. I haven't dug into any performance optimization yet though. |
|
Apr 15 |
comment |
ST_Intersection slow query The Max query ran faster than I expected: maxp = 2030 I suspect that's fairly fine grained? |
|
Apr 15 |
comment |
ST_Intersection slow query Hi LR1234567: "POSTGIS="1.5.2" GEOS="3.2.2-CAPI-1.6.2" PROJ="Rel. 4.6.1, 21 August 2008" LIBXML="2.7.6" USE_STATS";"PostgreSQL 9.0.3, compiled by Visual C++ build 1500, 32-bit" (running the other query now) |
|
Apr 15 |
comment |
ST_Intersection slow query Hi Mapperz: OS is Windows 7, CPU is Core 2 Duo, Memory is 4GB (being Windows, running 32-bit PGSQL / PostGIS) |
