topicmap: massive rework
Massively rework the way we build and use topicmap. This bring massive performance benefit. Topic map use to be a fully independant thing that we would switch on and off globaly. The caching on disk was broken so the performance were atrocious. Intead, now the topic are inherited from the 'immutable' map. We gave up on storing them on disk for now since the mutable set is usually small enough. The activation is done by hacking new "filter" on the repository and detection when they are one. This is hacky but core is hard to wrap here. Overall this whole wrapping is really scary and we should massage core API to help it.
Showing
- README 1 addition, 0 deletionsREADME
- hgext3rd/topic/__init__.py 17 additions, 14 deletionshgext3rd/topic/__init__.py
- hgext3rd/topic/destination.py 8 additions, 8 deletionshgext3rd/topic/destination.py
- hgext3rd/topic/discovery.py 30 additions, 25 deletionshgext3rd/topic/discovery.py
- hgext3rd/topic/topicmap.py 128 additions, 171 deletionshgext3rd/topic/topicmap.py
Loading
-
mentioned in commit 73034e07e6d1
-
mentioned in commit 7bcdda583f74
-
mentioned in commit 182e2a1dbd1c
Please register or sign in to comment