You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by "zccabb (via GitHub)" <gi...@apache.org> on 2023/05/06 07:10:02 UTC
[GitHub] [apisix] zccabb commented on issue #9196: Why APISIX rebuild radixtree every time when i edit router?
zccabb commented on issue #9196:
URL: https://github.com/apache/apisix/issues/9196#issuecomment-1537074509
I think it might be
Radixtree pursues maximum lookup performance, so both building and rebuilding need to be very efficient. Choosing to only support adding new nodes can simplify the implementation and improve performance.
If deleting old nodes and adding new nodes are used to update the radixtree, the implementation will be more complex and the efficiency will be difficult to reach the level of rebuilding a new radixtree.
As an auxiliary route lookup structure, the radixtree is accessed by a large number of requests. Even if it is rebuilt, it can be quickly rebuilt to meet performance requirements. This complete rebuild approach can achieve the simplest and most efficient implementation.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org