search

Google-Code-Fork / tibiaapi

Automatically exported from code.google.com/p/tibiaapi
MIT License
0 stars 0 forks source link

Review map algorithm #108

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
An algorithm used to read Map data fro memory is reported to be 
ineffective. Rewrite the algorithm to be more effective.

Original issue reported on code.google.com by Oskari.V...@gmail.com on 16 Jan 2009 at 7:36

GoogleCodeExporter commented 9 years ago 
What consumes less cpu, read all map from memory and store it in a local buffer 
or
read peaces of it?

Original comment by brunodun...@gmail.com on 19 Jan 2009 at 5:12

GoogleCodeExporter commented 9 years ago 
After reading this post: http://tpforums.org/forum/showthread.php?t=2911, I 
think I
will do some testing and check how much caching would speed it up.

Original comment by ian320 on 16 Mar 2009 at 1:01

GoogleCodeExporter commented 9 years ago 
I think the current system is good enough for what people will be using it for. 
I see
no need in caching anything, however, I'll leave this issue open for a decision 
from
Ian since he accepted it.

Original comment by joebingham07@gmail.com on 12 Nov 2009 at 7:28

GoogleCodeExporter commented 9 years ago 
This isn't really necessary. Users can do caching in their app if they want.

Original comment by ian320 on 12 Nov 2009 at 8:48