desteny

Thanks for the fast reply, only for information, this backport for oregoncore is based on two different repos, the first one is the this one https://github.com/faramir118/mangos/commits/mmaps_rewrite (the complete dep/recastnavigation, and map / vmap / mmap generator are complete the same) (small modifications based for 2.4.3) the pathfinder, and movemaps are also from this repo, but without spline (code doublechecked with the code used on mangos zero (https://github.com/mangos-zero/server/tree/feature/movemaps)) only the movement generators are based on a TC2 mmap backport, because there are to much differences between trinity and mangos. only one question, what is the most complete repo for the mmap rewrite? i was thinking it is this from faramir118? We have realy the intention to test and report problems here, and it makes no sense to make testing on a outdated code base thanks in advice

i can confirm this, on some large tables like characters and so on the index recalculation after delete and insert will produce a notable amount of workload for the database. and it even causes a kind of fragmentation witch could be optimized only with the mysql optimize command. my personal suggest is to use the INSERT .. ON DUPLICATE KEY UPDATE statement for SaveToDB methods, it will improve the database performance and reduces maintainance intervalls (optimize) and it even helps to keep the code more simple. (in some cases where you have to check) one word on the transactions: i think each update / insert statement should be executed in a transaction, because it perevents data loss ore inconsistency, of course the performance is not as good as dirty write, but who wants to loose data or have consistency problems? no one, and the most database querys (insert update) are executed async, for this reason it will not realy reduce the performance. I could not tell you if this is already like this on mangos, but at trinity it works like this (in the most cases) and it works fine

could someone tell me whats the status of the mangos-one mmap integration? i noticed that the spline integration is finished (i don't know if it is 100% finished) but there is nothing about mmaps (https://github.com/mangos-one/server) the mmap feature branch is not there any more since the repo was migrated tho the new one. but the old mmap branch was not realy up to date. Sorry for asking again, but is someone working on it, or not? if not maybe i will start backporting the mmaps from master, the only thing i want to avoid is to make senseless work [Edit] the actual branch is this one right? (https://github.com/faramir118/mangos/commits/mmaps_rewrite) the branch for mangos_one is not up to date (https://github.com/faramir118/mangos/commits/mmaps_one) better to use the mmap_rewrite branch as base, right?

there is no more mmap branch in the mangos-one/server repo, and the old one was not 100% updated right?

No Problem, a good Work needs Time, thank you all for your Work

is mangos one (mmap branch) ready for testing, or is it not finished yet?

Any News about this, great Project?