When to Semaphore vs Dispatch Group! Careful Multithreaded Shared Resource
Вставка
- Опубліковано 10 жов 2024
- Shared resources are often used across many different tasks in a multithreaded iOS application. If you want to make sure that a share resource is not accessed at the same time, you can guarantee the behavior through a Semaphore. However if your tasks are independent of one another, then using a Dispatch Group is probably the way to go.
AppStore JSON APIs
www.letsbuildt...
Tinder Firestore Swipe and Match
www.letsbuildt...
Twitter Slide Out Menu Course
www.letsbuildt...
Podcasts Course
www.letsbuildt...
Intermediate Training Core Data
www.letsbuildt...
Instagram Firebase Course
www.letsbuildt...
Facebook Group
/ 1240636442694543
Completed Source Code
www.letsbuildt...
Instagram: / buildthatapp
Twitter: / buildthatapp
Hackintosh Build
i9 9900k: amzn.to/2CvQj6v
ASUS Z390 Motherboard: amzn.to/2JpaQ2B
16GB Corsair Vengeance RGB RAM: amzn.to/2YbygvJ
Corsair H100i Platinum Water Cooler: amzn.to/2FnbM22
Thermaltake RGB Power Supply: amzn.to/2TgKDTu
Intel 1TB SSD: amzn.to/2Tkdk1V
Corsair 280x Computer Case: amzn.to/2WcjvH2
AMD Radeon 4GB RAM GFX Card: amzn.to/2TYMyAp
LG 34" Widescreen 3440 x 1440: amzn.to/2Tk7q0S
Rode NT1 Microphone: amzn.to/2TZgX1r
Focusrite Audio Interface: amzn.to/2U12gey
Panasonic GH4 DSLR: amzn.to/2U4BrG6
Magewell HDMI to USB3 Capture Card: amzn.to/2Jp2esI
Great video. I like that you're posting more advanced concepts in your channel.
Hey Brain, thanks for the video! You do good job and help people to learn iOS! I have one comment at 9:23 - it's not confusing, it's because you've set DispatchSemafore value to 0. The Semafore value represents how many treads can be executed at one point of time. When you call semaphore.wait(), you decreased value to -1. If semaphore's value is negative integer it is block execution of task, and system will wait when you release tread/treads which are in an awaiting state. What you did by replacing the lines of code, is at first you increased semaphore value to 1 (which is allow to run tasks on 1 tread at one point of time ), then fetchImage() was executing, then you decreased semaphore value back to 0 by calling semaphore.wait().
So, if you set DispatchSemafore value to 1 and return the order of lines of code, when you call at first semaphore.wait() and after fetchImage() semaphore.signal() - it will work.
Hi Brian, I can't count the number of times I clarified some concept by watching your videos. Thank you so much for all the work you're doing!
Thank you so much Brian! This video was incredible, I was able to use it to improve the user experience in our app when loading multiple images into a slideshow!
Thanks Brian. Please continue videos like this for advanced stuff. Now too many resources only for beginners.
Very detail and clear, Im 3 years iOS developer btw. Thank for give me more detail about this.
Extremely useful, especially when I was struggling with 2 async fetches that need to complete before continuing.
Advanced topics, interesting problems and great solutions. Thank you Brain
Helpful :) Expecting to share a single video which covers all advanced concepts
Props. I appreciate the advanced tutorials.
Amazing video, thank you so much!!!
Bold outfit
Thank you, Brian! Nice video and good explanation of what is going on. Can you please make more videos about multithreading?
Thanks Brian! Awesome video
You are awesome. Many thanks from Bulgaria :)
Group.Enter = semaphore.signal which increments semaphore..
For shared resource example dispatchGroup.wait() can be used
Thank you
The whole async for semaphores is in one block. Of course it will be executed in order, no semaphore would be needed there. Am I missing something?
Nice! Say, in a home page, if I want to display data section from top to bottom orderly, semaphore is the only way, right?
Hello Brian!
Why did u set value 0?
What if I set value 1?
DispatchGroup doesn't guarantee that your tasks will complete with the same order as when you submit it. If you want ordered you need to use wait(timeout:) method
This is gold 🎉
Hi I am a very big fan of your tutorial, In semaphore how to handle error cases, for example, consider there are 3 steps [API Call]
if step 1 got error then step 2 and step 3 should not run. How to do this?
10:31 that's a horrible concurrency code. At that point, you should just create a serial queue...
Is this semaphores technic similar to async await concept?
Awesome video and nice explanation!
Good video - I now know how dispatch groups work - although a little too basic. Could do a little more than just print. Still not sure why they fired in
that order. But will use that as a baseline for my application; hopefully it works.
I'm trying to do the following: NSURLSESSION to make a req to a db server in the cloud; get the data (XML), parse, then use the data (x,y coordinates)
to draw some bar graphs.
Thanks Brian! This was very interesting to watch :-D
Hi Brian, I have a doubt. How many API calls can do at a given point of time ?
I have a question what will happen if we call the above code inside any completion handler in swift instead of viewDidLoad?
Thanks for the information 👍
Hi Brian, I have a question about my case, I would like to find out how the differences between Semaphore and Dispatch Group resolve it
The problem: I would like to download 100 images
1. Case 1: If I would like to wait until 100 images are completely downloaded, I should use DispatchGroup
2. Case 2: If I would like to download 5 images and show them in UI, then to the next 5 images. I should use Semaphore.
Are they correct?
why not use async await ?
What do you mean by using async await?@@jasondubon
Also, I would like to understand in case we want to choose between DispatchGroup and Semaphore. Are they the correct way to use them? (even maybe they are not good approaches)@@jasondubon
Amazing video!!
Very nice
hi whats difference btw dipatch barrier and semophores ?
Awesome
Hey i just wanted to ask a question. I tryed using achor constraints and i did everything exactly like you did on screen but it wont let me use a anchor contraint from the view, which is the main view.
i keep getting a error. it says ancesters dont match . EXC_BAD_ACCESS......have you ever had that problem???
спасибо братишка за видосы)
Is it correct to use a semaphore in the method "cellForItemAt" of a uicollectionview, in order to wait for the previous images to load before new ones can be loaded? I'm loading those images from a shared resource inside the code, as you said in the video.
I'll respond to myself. yes.
I guess its wrong if you do not change the shared resources. Although I don't know reading at the same time brokes program. Why don't you use operatingqueue?
Better is dispatch queue barrier
I was thinking the same... That seems to be the better solution
Hey.. Please provide some tutorial on Apple Carplay Automaker
Why did you need to but it in a queue ?
Semaphores don't make a whole lot of sense when used on the main thread. Using it on a background queue allows for other things to run.
Only use Semaphore when you need to manage order of execution of background task.
Conclusion !!
Man this is a good one! xiexie!
If you are a Javascript developer, this is equivalent to async/await.
a little misleading unfortunately. semaphores are much more and have more uses than what you have discussed...
Thanks, but code style and API design is bad
Hi Brian. In your case you are always receiving all 3 elements in shared resource in DispatchGroup irrespective of its order. Same thing I tried with 5 calls and not everytime my shared resource count to 5. It is sometimes 4 or 3 as well. No APIs are failing. Is it due to dispatchGroup member modifying the same state of array so fast that the other one also receive the old state while modifying. Here was the group fb query post I posted. facebook.com/groups/swiftiosdev/1761808553978003/. Can you answer or provide some direction or I have to use Semaphore (Last option). For me ordering is not important
please try to explain slowly then it will better for learners
Hey Brian,
Using swift 5 Result type with DispatchGroups, would I need to include a dispatchGroup.leave() in the success case and the error case as well? Or just do it after the conditional statement checking success and errors?
Can u share an example ?
Hello man , please one video uploads in firebase chat app create user chat send msg display on top user in Android function
On ua-cam.com/video/6rJN_ECd1XM/v-deo.html, if you change the value from 0 to >1, it will work perfectly fine as it is the number of threads you are allowing it to access. Right now it's 0 that's why it is not print anything. Why it started working was, when you executed 'semaphore.signal()' it incremented the count from 0 to 1, after that execution worked smoothly.
Great video BTW, Waiting for more videos from you :)