|
Date |
User |
Action |
Args |
2019-01-21 13:55:06 | malte | set | messages:
+ msg8492 summary: * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844)
* Consider deque instead of vector for IntHashSet because it can deal with
fragmented memory.
* If we use a deque for IntHashSet, consider growing it in place when resizing.
(This complicates rehashing.)
* Cache heuristic values by default only for a subset of the heuristics
(issue579)
- Reduce memory usage of causal graph heuristic cache (issue838) -> * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844)
* Consider deque instead of vector for IntHashSet because it can deal with
fragmented memory.
* If we use a deque for IntHashSet, consider growing it in place when resizing.
(This complicates rehashing.)
* Cache heuristic values by default only for a subset of the heuristics
(issue579)
* Reduce memory usage of causal graph heuristic cache (issue838) |
2019-01-21 13:51:46 | jendrik | set | messages:
+ msg8490 summary: * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844)
* Consider deque instead of vector for IntHashSet because it can deal with
fragmented memory.
* If we use a deque for IntHashSet, consider growing it in place when resizing.
(This complicates rehashing.)
* Cache heuristic values by default only for a subset of the heuristics
(issue579) -> * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844)
* Consider deque instead of vector for IntHashSet because it can deal with
fragmented memory.
* If we use a deque for IntHashSet, consider growing it in place when resizing.
(This complicates rehashing.)
* Cache heuristic values by default only for a subset of the heuristics
(issue579)
- Reduce memory usage of causal graph heuristic cache (issue838) |
2017-01-11 18:58:08 | haz | set | nosy:
+ haz summary: * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844)
* Consider deque instead of vector for IntHashSet because it can deal with
fragmented memory.
* If we use a deque for IntHashSet, consider growing it in place when resizing.
(This complicates rehashing.)
* Cache heuristic values by default only for a subset of the heuristics (issue579) -> * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844)
* Consider deque instead of vector for IntHashSet because it can deal with
fragmented memory.
* If we use a deque for IntHashSet, consider growing it in place when resizing.
(This complicates rehashing.)
* Cache heuristic values by default only for a subset of the heuristics
(issue579) |
2016-12-19 13:51:00 | jendrik | set | summary: * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844)
* Consider deque instead of vector for IntHashSet because it can deal with
fragmented memory.
* If we use a deque for IntHashSet, consider growing it in place when resizing.
(This complicates rehashing.) -> * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844)
* Consider deque instead of vector for IntHashSet because it can deal with
fragmented memory.
* If we use a deque for IntHashSet, consider growing it in place when resizing.
(This complicates rehashing.)
* Cache heuristic values by default only for a subset of the heuristics (issue579) |
2016-12-12 23:35:08 | malte | set | status: unread -> chatting messages:
+ msg5869 summary: * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844)
* Consider deque instead of vector for IntHashSet, because it doesn't require
contiguous memory and can grow in place. However, this would complicate the
rehashing code. -> * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844)
* Consider deque instead of vector for IntHashSet because it can deal with
fragmented memory.
* If we use a deque for IntHashSet, consider growing it in place when resizing.
(This complicates rehashing.) |
2016-12-12 14:44:42 | jendrik | set | summary: * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844) -> * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844)
* Consider deque instead of vector for IntHashSet, because it doesn't require
contiguous memory and can grow in place. However, this would complicate the
rehashing code. |
2016-11-30 22:41:56 | jendrik | set | summary: * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844) -> * make 64-bit build more memory-efficient (issue213)
* log maximum open-list size and compare to number of generated states (msg5844)
* use more aggressive duplicate elimination if open-list size is a bottleneck
(msg5844) |
2016-11-30 21:13:09 | jendrik | create | |