Skip to main content
11 events
when toggle format what by license comment
Feb 26, 2018 at 15:51 comment added MSalters @KonradRudolph: Well, I think we would agree that virtually noone is going to be using TSX straight from assembly. There will be higher-level abstractions. Will those abstract transactions be SQL transactions? I think not. As an interpreted language, SQL carries a performance overhead. That really didn't matter when you accessed data on rotating harddisks. It is unaffordable however when accessing data in RAM.
Feb 26, 2018 at 15:22 comment added Konrad Rudolph @MSalters Aren’t we on a completely different layer here though? Hardware TM is all nice and well but does it work with complex memory access patterns? How easy is controlling it in high-level languages (caveat: I know virtually nothing about hardware TM, these are genuine questions)?
Feb 26, 2018 at 15:18 history edited Robert Baron CC BY-SA 3.0
added 164 characters in body
Feb 26, 2018 at 15:15 comment added MSalters @KonradRudolph: Well, that is where R. Martin has a point. Transactions are moving to the CPU. Xeon has TSX, and soon can use TSX on Optane storage and RAM alike.
Feb 26, 2018 at 14:34 comment added user251748 Maybe it is a very short mixture of Visual Basic and Fortran. Where will it all END?
Feb 26, 2018 at 14:13 history edited Robert Baron CC BY-SA 3.0
added 164 characters in body
Feb 26, 2018 at 13:56 comment added Konrad Rudolph @nocomprende So you’re saying that he’s the victim of a race condition? Well, oops. He could have avoided that by using SQL transactions.
Feb 26, 2018 at 13:48 history edited Robert Baron CC BY-SA 3.0
added 164 characters in body
Feb 26, 2018 at 13:36 comment added user251748 It is a word order issue. Actually this was originally a telegram: USING SQL STOP
Feb 26, 2018 at 13:31 comment added Doc Brown "STOP USING SQL" (cited from the first link) sounds very much like he is saying not to use SQL, to my understanding.
Feb 26, 2018 at 12:32 history answered Robert Baron CC BY-SA 3.0