3 ms·

I'm just guessing here but this to me seems a bit too micro optimization. Great when you are a huge company with massive number of data and operations where ev

by Kesty 10y ago

I'm just guessing here but this to me seems a bit too micro optimization. Great when you are a huge company with massive number of data and operations where every ms counts, but in most cases there are bigger and more important things to optimize before saving some round trips from the db.

qaq 10y ago
If you use sps you actually have much less coupling to the structure of your DB that let's you rearrange/optimize things on DB side without affecting the client apps. Plus you can gain serious security benefits by using sps only.
jhugg 10y ago
It’s totally true that this optimization only matters if you’re pushing your database. Of course as a VoltDB employee, we have a number of smaller customers who use VoltDB because it allows a small shop to do things that would be too expensive with a traditional system. Just because you’re small, doesn’t mean you don’t have a high-throughput problem. One example is Xacte, which tracks marathon bibs as they fly by RFID sensors in the course. The issue is when 50 people run by a sensor in one second, the de-duplification code in the sensor sometimes breaks down, and their system gets hundreds of triggers. They literally have a van full of equiptment that includes a small VoltDB cluster keeping accurate runner positioning for events like the LA Marathon.
ajmurmann 10y ago
Round trips over the network of any kind are actually the fastest way to make your application slow. So if you do optimize for performance then this is a good starting point, if you do go over the network a lot. But you are right that you should think twice and first make sure you even built the right thing.
- Kesty 10y ago
  Yes, I agree. But, in many (if not most) situations the ms you loose by doing more round trips then necessary are not worth how much more maintainable the system is. Especially when there is probably some programming or query optimization that will save you seconds, when reducing the round trips is a matter of ms.
  - Jweb_Guru 10y ago
    It's very system dependent, but VoltDB is designed for systems that require up to a million tps. "A matter of ms" is not irrelevant in such systems.
    - Kesty 10y ago
      Yes, ok I agree. 100% agree. But micro optimization has always the same caveat: Of course it is not irrelevant, it might even be very important, in very specific cases. But if you are not one of those cases (and you should already know if you are) you shouldn't even bother with it.
      - Jweb_Guru 10y ago
        I think that everything you just said categorizes VoltDB already, though. They're not advertising themselves as a general purpose database. You'll know if you have a use case for it.

by Kesty 10y ago

qaq 10y ago

If you use sps you actually have much less coupling to the structure of your DB that let's you rearrange/optimize things on DB side without affecting the client apps. Plus you can gain serious security benefits by using sps only.

jhugg 10y ago

It’s totally true that this optimization only matters if you’re pushing your database. Of course as a VoltDB employee, we have a number of smaller customers who use VoltDB because it allows a small shop to do things that would be too expensive with a traditional system. Just because you’re small, doesn’t mean you don’t have a high-throughput problem. One example is Xacte, which tracks marathon bibs as they fly by RFID sensors in the course. The issue is when 50 people run by a sensor in one second, the de-duplification code in the sensor sometimes breaks down, and their system gets hundreds of triggers. They literally have a van full of equiptment that includes a small VoltDB cluster keeping accurate runner positioning for events like the LA Marathon.

ajmurmann 10y ago

Round trips over the network of any kind are actually the fastest way to make your application slow. So if you do optimize for performance then this is a good starting point, if you do go over the network a lot. But you are right that you should think twice and first make sure you even built the right thing.

Kesty 10y ago
Yes, I agree. But, in many (if not most) situations the ms you loose by doing more round trips then necessary are not worth how much more maintainable the system is. Especially when there is probably some programming or query optimization that will save you seconds, when reducing the round trips is a matter of ms.
- Jweb_Guru 10y ago
  It's very system dependent, but VoltDB is designed for systems that require up to a million tps. "A matter of ms" is not irrelevant in such systems.
  - Kesty 10y ago
    Yes, ok I agree. 100% agree. But micro optimization has always the same caveat: Of course it is not irrelevant, it might even be very important, in very specific cases. But if you are not one of those cases (and you should already know if you are) you shouldn't even bother with it.
    - Jweb_Guru 10y ago
      I think that everything you just said categorizes VoltDB already, though. They're not advertising themselves as a general purpose database. You'll know if you have a use case for it.