Code Review / multicloud / framework.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 7850f68) | patch
Migrate get vim_types to new framework 77/34677/2
authorHong Hui Xiao <honghui_xiao@yeah.net>
Thu, 8 Mar 2018 06:19:54 +0000 (14:19 +0800)
committerHong Hui Xiao <honghui_xiao@yeah.net>
Fri, 23 Mar 2018 02:42:55 +0000 (10:42 +0800)
commita137643d7f753d1b26f0d7863912264e7c49a2fe
tree1e1f46c002b6a551bf78d500941d31d4ddb91aa0tree | snapshot
parent7850f681fb63a7dca983accd42433926334fd287commit | diff
Migrate get vim_types to new framework

A simple comparison between new framework and old framework can
be found at [1]. In a high concurrent situation, new framwork
is 24 times faster than old one. Since get vim_types is less
overhead, result in [1] is more convincing to just compare frameworks.

[1] https://paste.ubuntu.com/p/Nc5WTgsKNP/

Change-Id: I0bd3ada0684cb20319895ced77d10d8593873eee
Issue-ID: MULTICLOUD-150
Signed-off-by: Hong Hui Xiao <honghui_xiao@yeah.net>
multivimbroker/multivimbroker/api_v2/api_router/v0_controller.py diff | blob | history
multivimbroker/multivimbroker/forwarder/views.py diff | blob | history
multivimbroker/multivimbroker/pub/utils/syscomm.py diff | blob | history
Common components for multicloud framework