In this issue: TechEd / Tech Connect: It’s The Stories Odoo Redux ABAPosaurus Goes to Virtual TechEd Faster Horses of CDS AI Iron Man, or AI Thanos? Tech Connecting: Mission Accomplished As always, thanks for reading! TechEd / Tech Connect: It’s The Stories
We all know about "meeting that should've been an email" and there are too many of "session that should've been a blog post". I've heard from some people that they go to the roadmap sessions and find them valuable. What I want to ask every time: did you really have to travel to a live event for this though? The roadmap explorer is out there online. Is it really necessary to have like a public ("Hear ye, hear ye...") reading of the document?
Nov 28, 2023Liked by Paul Modderman, Jelena Perfiljeva
Look mom I'm famous, I've got my picture on the internet! It's funny to compare your session ranking to what we got at OXP, the customer stories are not as interesting as the learning and new features. And roadmap are always asked about during AMA, but Odoo generally refuses to communicate on features before they're developed.
Nov 15, 2023Liked by Paul Modderman, Jelena Perfiljeva
Re: It’s the stories -- I totally agree. The best TechEd presentation I saw was about how InfoZoom architected one of their processes with BTP and Stripe.
What makes you think that HANA is faster than ordinary relational databases? I mean, outside SAPs marketing? Even Hasso Plattner himself expects a 10% gain in speed at best on transactional processing once the index btree is already cached by the db-system. While in ordinary DBs you have to read the record from the hard disk, in HANA you have do go through decompression and tupel- reconstruction. In memory it's faster but considerably more workload.
In-memory DB has advantages when using aggregates. But honestly, outside analytical processing there is very very very little need for using aggregates.
What is left is that you have to rework you old code so it does not slower on HANA than with you old Oracle system, e.g. replacing SELECT * with a field list in the SELECT to limit the dictionary lookups for decompression.
We all know about "meeting that should've been an email" and there are too many of "session that should've been a blog post". I've heard from some people that they go to the roadmap sessions and find them valuable. What I want to ask every time: did you really have to travel to a live event for this though? The roadmap explorer is out there online. Is it really necessary to have like a public ("Hear ye, hear ye...") reading of the document?
Look mom I'm famous, I've got my picture on the internet! It's funny to compare your session ranking to what we got at OXP, the customer stories are not as interesting as the learning and new features. And roadmap are always asked about during AMA, but Odoo generally refuses to communicate on features before they're developed.
@jelena - how many years did you hear me scream about the power of customer stories?
Re: It’s the stories -- I totally agree. The best TechEd presentation I saw was about how InfoZoom architected one of their processes with BTP and Stripe.
What makes you think that HANA is faster than ordinary relational databases? I mean, outside SAPs marketing? Even Hasso Plattner himself expects a 10% gain in speed at best on transactional processing once the index btree is already cached by the db-system. While in ordinary DBs you have to read the record from the hard disk, in HANA you have do go through decompression and tupel- reconstruction. In memory it's faster but considerably more workload.
In-memory DB has advantages when using aggregates. But honestly, outside analytical processing there is very very very little need for using aggregates.
What is left is that you have to rework you old code so it does not slower on HANA than with you old Oracle system, e.g. replacing SELECT * with a field list in the SELECT to limit the dictionary lookups for decompression.