Latency between action call and execution start is too long
Bug #1481950 reported by
Serg Melikyan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Murano |
Invalid
|
Wishlist
|
Serg Melikyan | ||
Bug Description
Our package loader/class loader are very inefficient, we need to make sure that we can start executing action in milliseconds after action call.
| summary: |
- Latency between action call and execution starts is too long + Latency between action call and execution start is too long |
Revision history for this message
| Kirill Zaitsev (kzaitsev) wrote | #1 |
| Changed in murano: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
| milestone: | liberty-3 → 2015.1.1 |
Revision history for this message
| Ekaterina Chernova (efedorova) wrote | #2 |
| Changed in murano: | |
| milestone: | 2015.1.1 → next |
| assignee: | nobody → Serg Melikyan (smelikyan) |
| Changed in murano: | |
| milestone: | next → mitaka-1 |
| Changed in murano: | |
| milestone: | mitaka-1 → mitaka-2 |
Revision history for this message
| Stan Lagun (slagun) wrote | #3 |
| Changed in murano: | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
We might want to cache packages/classes in memory (or in caching server, say redis/memcached) and support If-Modified-Since header on API side. This would greatly reduce network usage, as engine would only need to check if there is a newer version of the class available, not request the class every time.
Feels more like a small feature than a bug though.