You guys are amazing. Love to watch your videos and learn new things.
@sampleshawn5380 Жыл бұрын
Man you are awesome, i am binge watching your stuff, kudos
@PlanetScale Жыл бұрын
Thank you!
@wagnerbugs Жыл бұрын
Do you know what the only problem with this channel is? Without a doubt, it's not having videos every day. 😂 Congratulations on yet another great video. ❤
@PlanetScale Жыл бұрын
Thank you!
Жыл бұрын
This guy is very smart
@VuTuanIT11 ай бұрын
I didn't give it a try but I'm curious: - The cache is updated in sync or async? will the updates be available right after we write the new values? - Will the cache work well on heavy write tables? Something like a data logs table that can have a thousand rows written per second
@m.h.6470 Жыл бұрын
As someone who works with bigger databases and complex queries on a daily basis, I can say, that this is quite unrealistic. The queries that take a lot of time are not the queries, that are run over and over again. Those repeated queries are usually optimized already. The big long queries are the queries that are very complex and have many dynamic parts (like different where clauses, changing group conditions, etc.) and can therefore not be cached or optimized in the way you are saying.
@captainchaos36679 ай бұрын
If something sounds too good to be true, that's probably because it's not true. If it was this easy to make every query a thousand times faster everyone would do that. Disappointing to see clickbait on this channel, but good to know.
@arthurmagamedov3179 Жыл бұрын
That's nice!! It's like IBM DB2 version of MQT with MAINTAIN BY SYSTEM option, but created automatically! That's cool!!
@GoncaloMangana Жыл бұрын
So, the more materialized cached views you have using the same tables, the worst the write performance will be? How much impact does it have? I'm curious if it is an acceptable trade off, like if you get an extra 2s on a write but gain 60s on a read, I would be ok with that. Could you shed some light please?
@spicynoodle7419 Жыл бұрын
Write-through cache
@PlanetScale Жыл бұрын
It's similar but PlanetScale Boost is more performant and less to maintain.
@spicynoodle7419 Жыл бұрын
@@PlanetScale I shall get to the bottom of this dark magic
@WaltersWatching Жыл бұрын
You'd think a cache would be affordable, $100/month minimum is wild.
@otmanm4095 Жыл бұрын
This guy is very strong
@ucretsiztakipci6612 Жыл бұрын
Excellent feature but too expensive.
@TomandJerryaredead9 ай бұрын
Does Boost support ORDER BY queries? And does it support the use of NOW() in a WHERE clause?
@jwbonnett9 ай бұрын
Sounds the same as a projection
@DirkSchut9 ай бұрын
Probably never gonna need this, but I'm curious why an 8GB cache is more than 8x as expensive as a 1GB cache.
@pinguluk1 Жыл бұрын
What are the disadvantages?
@ropoxdev11 ай бұрын
Cost, but it’s free during beta
@StevenGlrz Жыл бұрын
Does this have a penalty on write performance?
@blazed-space Жыл бұрын
You guys have gotten my business, your product is amazing and prioritizes speed and affordability which is key for me
@DerClaudius8 ай бұрын
Quick question... the switching looked instant, although I would expect that at least the first execution of the query should still be slow to fill the boost cache and setup the change listeners.. Did you just skip that for the vid?
@PlanetScale8 ай бұрын
Boost fills the cache in the background. So until Boost is ready the queries don't run through it. As far as listeners, it just subscribes to the existing Vitess events so that part is pretty lightweight
@micha-ix1iy Жыл бұрын
Is this eventuell consistent or does writing block until boost’s caches are updated?
@user-ve9ix1fe9e11 ай бұрын
Hi, that's great! Is there any introduction to the implementation of the boost acceleration function in the source code?
@PlanetScale10 ай бұрын
The most technical documents we have on the implementation would be in the linked blog post! I think in the blog post there is also a link to the academic paper it's based upon
@user-ve9ix1fe9e10 ай бұрын
@@PlanetScale This OSDI ’18 paper is really very detailed. I would like to know more code details. Is the source code of Boost function public? So which file is the entrance to the implementation in the github warehouse?😀
@faiz_00009 ай бұрын
10:32 what about the data that already exist in the database? do you rewrite the entire data or just move the existing data to cache based on the query that we want to boost
@SeyedaMansour Жыл бұрын
Just found your chanel, can't stop watching :D, great videos so far, keep up the good work. For things like this i tend to to add a redundant (count/calc/processed) column to the table and update it on created_at/updated at, it does just fine. your method is probably faster since you do less with db but u use more non-db resources, so it's trade off i guess.
@pau1phi11ips11 ай бұрын
Same 🤓
@dechobarca Жыл бұрын
Why does a simply query that returns just a thousand records take almost an entire second in first place?
@PlanetScale Жыл бұрын
It's joining in a table that's an aggregate over a few million rows
@dechobarca Жыл бұрын
@@PlanetScale ah I see, my bad. I don't use planetscale myself, but you do have some good SQL videos, so keep up the great work, cheers!
@jacekkangaroo4402 Жыл бұрын
I hate when people do not use table/view aliases, it is a very bad habit, it makes complex queries difficult to analyze
@aarondfrancis Жыл бұрын
This guy is very me
@OrangeNerd1 Жыл бұрын
light mode 🤨
@aarondfrancis Жыл бұрын
@@OrangeNerd1 ¯\_(ツ)_/¯
@Guilherme-qk9so Жыл бұрын
Very cool!
@icebox747 Жыл бұрын
Anyone knows the Vetez he is mentioning in the video?
@PlanetScale Жыл бұрын
vitess.io!
@michelvandermeiren866111 ай бұрын
Impressive ! Is the web interface for continuous testing opensource ?
@PlanetScale11 ай бұрын
No unfortunately not!
@GottZ Жыл бұрын
The auto creation of triggers to update cached representations / views on the fly on data changes sure is impressive.. how ever.. isn't this 101 of database architecture, anyone creating proper databases should know? This feels like a feature primarily targeted towards people with lacking database knowledge. Especially the video title.
@PlanetScale Жыл бұрын
Sorry if it wasn't clear, this does not rely on triggers or views. It creates a query plan, inverts it, and incrementally updates the cache as new writes come in. It works for more than just counts, and it doesn't run the entire query again. The attached blog post goes into more detail if you're interested.
@adarshchacko6137 Жыл бұрын
Curious question: Between the 2 which is faster and why ? QUERY 1: SELECT * FROM users; QUERY 2: SELECT FROM users;
@gileee Жыл бұрын
Selecting a single column is less data. Less data needs to be read from storage, sent over the network and in the end displayed/processed, so it'll be faster. "*" in general means the db will need to first fetch what columns exist on that table in order to retrieve them. So it's never ideal for performance, even if you need all the data.
@adarshchacko6137 Жыл бұрын
@@gileee Thanks Didn't quite get the last part though "So it's never ideal for performance, even if you need all the data." What is not ideal... "SELECT *" ??
@gileee Жыл бұрын
@@adarshchacko6137 Yeah. If you do * apparently the db has to first fetch the definition of the table to figure out which columns it has. So it would be slightly more performant to write "SELECT col1, col2, ..." and list all the columns.
@adarshchacko6137 Жыл бұрын
Understood... Thank you @gileee
@ComfyCosi Жыл бұрын
Lenseless glasses T_T
@aarondfrancis Жыл бұрын
🥸
@frederikadmiralshi4080 Жыл бұрын
Can’t be the only one that ended up feeling this was an Ad disguised as a video. 👎🏻😞
@fuxtnegrx Жыл бұрын
Error Code: 1193. Unknown system variable 'boost_cached_queries' 0.141 sec
@kskredderbakken10 ай бұрын
why isn't boost standard......?
@kskredderbakken10 ай бұрын
HOW isn't he question. WHY is the question. We have good enough chips to leave 1980 behind.
@PlanetScale10 ай бұрын
It's a good question! The research paper was only released recently. We're among the few people in the world that have implemented it at a production grade. It's tough to deconstruct queries and apply partial updates to caches upon write instead of rerunning entire queries, so that's my guess.
@mainakdas5819 Жыл бұрын
What is the application used for running SQL query?
@isakhansson917 Жыл бұрын
He literally said it in the video?
@PlanetScale Жыл бұрын
TablePlus!
@mainakdas5819 Жыл бұрын
@@isakhansson917 maybe I missed 😅
@GackFinder11 ай бұрын
5:28
@pietraderdetective895311 ай бұрын
Amazing! Love planetscale coz of these improvements they're doing 👍🏻
@stefanotorelli3688 Жыл бұрын
You forgot to explain the architecture of your solution, even if it OOB in MySQL.
@chinheiyung1303 Жыл бұрын
What is the sql client are you using? Look so sleek
@PlanetScale Жыл бұрын
TablePlus!
@martintsekov7820 Жыл бұрын
Quite weird that he wears fake glasses..
@daguttt Жыл бұрын
Sheeeesh
@yousafwazir286 Жыл бұрын
How dose it make it 1000 x faster ?
@PlanetScale Жыл бұрын
Boost deconstructs the query plans and applies incremental updates to the cache when data is updated. For more details check out the video or the linked post!
@vickoalan Жыл бұрын
if we use Planetscale Boost we don't need caches like radius right???
@PlanetScale Жыл бұрын
For queries that are Boosted, you would no longer need a cache!
@Alekzv9 Жыл бұрын
This guy is very handsome
@dn5426 Жыл бұрын
your last name checks out!
@mehboobfazal Жыл бұрын
Pretty old days my mysql 😊. Love to see this happen. I'll really give a shot in my next upcoming project.
@ousspero Жыл бұрын
This is what we call a View
@obapelumi Жыл бұрын
Not necessarily. A view gets re-created/re-calculated whenever it is read/queried. With planet scale boost it is re-calculated when the underlying data which the query represents is written to
@PlanetScale Жыл бұрын
Kind of! In the video I explain why it's like a view, but fundamentally quite different.