I've been thinking this too.
I've been thinking this too. For example, it is very easy to write badly performing code using ORMs. And yet, ORM is often chosen for good reasons initially to give development speed (e.g. Django forms) The problem with quickly prototyped ORM based apps is that initially the performance is good enough but when the data grows the amount of queries goes through the roof. It is not the amount of data per se, but number of queries. Fixing these performance problems afterwards for small customer projects is often too expensive for the customer, but if there were a plug'n'play in-memory SQL cache/replica with disk-based writes, it would easily handle the problem for many sites. Configuring PostgreSQL to do something like reading data from in-memory replica is likely possible, but I see that there would be value in plug'n'play configuration script/solution.
Posted by dirtyaura on May 21, 2015, 2:47 PM
Tags
Related issues
- Not at all, actually.
- A car battery with reduced range is still perfectly useable as a storage battery for a PV system.
- Here in Argentina we are in permanent summer time GMT-3 since a long time, but we should be in GMT-4.
- You should do some basic research yourself.
- Well, actually not.
- I have a 2022 mini that I use constantly.
Raise real-world problems, find people facing the same issue, and discuss solutions.6,500 issues0 comments
pricing (Other)
Not at all, actually.
NewA car battery with reduced range is still perfectly useable as a storage battery for a PV system.
NewHere in Argentina we are in permanent summer time GMT-3 since a long time, but we should be in GMT-4.
NewYou should do some basic research yourself.
NewWell, actually not.
I have a 2022 mini that I use constantly.
Two observation: 1.
Cautiously optimistic for them.
I've been thinking this too.
I've been thinking this too. For example, it is very easy to write badly performing code using ORMs. And yet, ORM is often chosen for good reasons initially to give development speed (e.g. Django forms) The problem with quickly prototyped ORM based apps is that initially the performance is good enough but when the data grows the amount of queries goes through the roof. It is not the amount of data per se, but number of queries. Fixing these performance problems afterwards for small customer projects is often too expensive for the customer, but if there were a plug'n'play in-memory SQL cache/replica with disk-based writes, it would easily handle the problem for many sites. Configuring PostgreSQL to do something like reading data from in-memory replica is likely possible, but I see that there would be value in plug'n'play configuration script/solution.
Comments (0)
No comments yet. Start the discussion.