Apparent memory leak in traffic engine

opentraffic / architecture

OTv1 overview

71 stars 11 forks source link

Apparent memory leak in traffic engine #22

Closed bmander closed 9 years ago

bmander commented 9 years ago

At about 43 million points, the thing consumes 4gb of memory and grinds to a halt. There's no good reason that should happen.

bmander commented 9 years ago

Implemented with 4e9a77455b26d1caf55d865bd0e34097eca77264. There was no memory leak. Rather, the traffic datastore was slowly filling, and when filled it would have occupied more in-memory space than available. Problem fixed by moving to MapDB.