Timeline for Caching or in-memory table in Azure for performance
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 2, 2020 at 18:55 | comment | added | Tanmoy Sengupta | @RobertHarvey what's your suggestion to play with 33 MB (with possible growth in future) of data? I can't transfer all the data on client side (browser) as I need to keep the payload lean due to the the low latency of 3G connection. The API layer consists of stateless Azure Functions (cannot use Durable Functions as we are using Python). What options do I have other than using an in-memory store/cache like Azure Redis or SQL in-memory OLTP? | |
| Jun 2, 2020 at 18:53 | comment | added | Telastyn | No, on the server side... your option 2 (though I would recommend something far simpler than you’re imagining) | |
| Jun 2, 2020 at 18:39 | comment | added | Robert Harvey | You don't have 33 MB available to play with? | |
| Jun 2, 2020 at 18:28 | comment | added | Tanmoy Sengupta | Which RAM? Did you see the tech stack? | |
| Jun 2, 2020 at 18:22 | comment | added | Telastyn | 33 MB? Toss it in ram. No need to make things complicated. | |
| Jun 2, 2020 at 18:20 | comment | added | Tanmoy Sengupta | Sorry it's 80k records (30k was a typo which I corrected now). The total data size of this table on SQL DB is 33 MB. | |
| Jun 2, 2020 at 18:18 | history | edited | Tanmoy Sengupta | CC BY-SA 4.0 | edited body |
| Jun 2, 2020 at 15:21 | comment | added | Telastyn | How big are your 30k records? | |
| Jun 2, 2020 at 0:55 | answer | added | Greg Burghardt | timeline score: 1 | |
| Jun 2, 2020 at 0:24 | history | edited | Tanmoy Sengupta | CC BY-SA 4.0 | added 2 characters in body |
| Jun 1, 2020 at 23:51 | history | asked | Tanmoy Sengupta | CC BY-SA 4.0 |