• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
lipsryme

Multithreaded job/task design help (Dependencies)

1 post in this topic

I'm currently trying to get my head around how to implement the dependencies of tasks onto other tasks in such a system.

For priority of tasks my task object stores a priority value -> priority_queue gives me the task with the highest priority.

But the problem is for defining dependencies like e.g. a render task having dependency on a physics task to finish its work.

Can someone tell me / give me an example on how this is done right ?

 

 

Another small question...do I take tasks as they come or do I first fill the queue with tasks for e.g. the entire frame and then schedule it ?

 

I'm currently looking at Intel Building Blocks. Is it worth using ?

Edited by lipsryme
0

Share this post


Link to post
Share on other sites

I'm currently trying to get my head around how to implement the dependencies of tasks onto other tasks in such a system.
For priority of tasks my task object stores a priority value -> priority_queue gives me the task with the highest priority.
But the problem is for defining dependencies like e.g. a render task having dependency on a physics task to finish its work.
Can someone tell me / give me an example on how this is done right ?


One way is for each task to simply have a list of things that depend on it.

Let's look at the simple case of each task having at most a single dependency. You have a global queue of pending tasks. Each task has a list of dependencies. When a task is created, only add it to the global queue if it has no outstanding dependencies. Otherwise, add it to the dependent list on the task it depends on. When a task is completed, move all the tasks in its dependent list to the pending task queue.

Extending this to allowing multiple dependencies mostly just entails adding a reference count. When a task completes, loop over its dependent tasks and decrement their "pending_dependency" count by 1. If the count hits 0, all dependencies have completed and the task is ready to be moved into the pending queue. If the count is greater than 0, the task is still waiting on something, so do nothing.

If tasks can fail, all dependent tasks should also be marked as failed (recursively) to avoid "stuck" tasks from failures leaking.

I would just avoid most of this, though. I can see good uses for dependencies in complex resource chain loading, but in main engine code I tend to advocate the fork-join model of threading. Instead of trying to queue up physics and render jobs simultaneously (do all render jobs depend on all physics jobs?), do one at a time. In your main loop, your physics update just adds a bunch of physics jobs. The loop then waits for all those jobs to complete. Then it might move on rendering and generate all the jobs and then wait for it to finish. It's a _significantly_ easier model to work with as you have a much stricter and easier to manage set of data dependencies between threads.
  

Another small question...do I take tasks as they come or do I first fill the queue with tasks for e.g. the entire frame and then schedule it ?


Try both, see what works better. The only way you can _ever_ accurately reason about performance is to actually measure and compare, assuming that's your primary concern here.
 

I'm currently looking at Intel Building Blocks. Is it worth using ?


There's no strong reason not to if you like it and it does what you want. It's not horribly broken or anything.
2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0