<transcript><audio_244>something called a master page page table kind of like your operating system those of youve taken an operating system class know that there's a page mapping table from your virtual address space to a physical address space right kind of like that but not that complicated here</transcript><transcript><audio_245>is just saying uh page one is this page this disk position uh in my stable storage okay it's just a pointer it's just a uh list of where the pages are and when the transaction comes in it will make a copy of that page table</transcript><transcript><audio_246>effectively think of it as getting a snapshot by virtue of copying this and now when it makes changes it's going to make changes if page one has to be updated it'll make a new copy of that page a shadow make a full new copy of</transcript><transcript><audio_247>itself of that page make changes just there so if some of the transaction is making changes to page one it'll make another full copy of page one uh and there ways to merge it and combine that but assume it just as one at a time and then effect L all the changes will</transcript><transcript><audio_248>create new pages those are only pointed to by my shadow page table copy and then ultimately when I'm ready to commit I will do the following which is I'll take the there's a point R memory to the root of the master page table which is pointing to the old page</transcript> something called a master page page table kind of like your operating system those of youve taken an operating system class know that there's a page mapping table from your virtual address space to a physical address space right kind of like that but not that complicated here is just saying uh page one is this page this disk position uh in my stable storage okay it's just a pointer it's just a uh list of where the pages are and when the transaction comes in it will make a copy of that page table effectively think of it as getting a snapshot by virtue of copying this and now when it makes changes it's going to make changes if page one has to be updated it'll make a new copy of that page a shadow make a full new copy of itself of that page make changes just there so if some of the transaction is making changes to page one it'll make another full copy of page one uh and there ways to merge it and combine that but assume it just as one at a time and then effect L all the changes will create new pages those are only pointed to by my shadow page table copy and then ultimately when I'm ready to commit I will do the following which is I'll take the there's a point R memory to the root of the master page table which is pointing to the old page
{"source": "grass-yt-cc-by.-mY8ALcJVTk|shard_1_1|create_multimodal_data.extract_yt_and_generate_transcripts.62|shard_1|create_multimodal_data.generate_captions.62|shard_1|create_multimodal_data.generate_captions.62", "params": {"id": "-mY8ALcJVTk", "channel_id": "UCHnBsf2rH-K7pn09rb3qvkA", "duration": 5000, "view_count": 4483, "age_limit": 0, "like_count": 50, "channel_follower_count": 71100, "license": "Creative Commons Attribution license (reuse allowed)", "uploader_id": "@CMUDatabaseGroup", "yt_tar_file": "/leonardo_work/EUHPC_E03_068/audio/fixed_download/grass-yt-cc-by//shard_1/-mY8ALcJVTk.tar.gz"}}