Skip to content

[Refactor] discussion of applying spring In-memory Cache to improve ordering engine #4

@platypus3036

Description

@platypus3036

Is your feature request related to a problem? Please describe.

  • In the process of mixing two types of engines, we thought spring in-memory cache could improve our engine performance.

Describe the solution you'd like

last version
KIS API Data <-> Ordering condition <-> Compare orderingQueue
=> have no reason for using Cache. only improving reading behavior couldn't be reason of using cache.
Ordering data changes almost 10 times per seconds. reading data throught cache could improve  reading speed, but another action (checking cache, searching cache, write data into the cache) could interrupt another spring process. 

Describe alternatives you've considered
Changing Data Queue type or optimizing synchronizing method could be better solution of improving engine.

Additional context
We must consider the reason why we use that skill.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions