• 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
IceCave

Multithreading synchronization problem

5 posts in this topic

First of all: Hi.

Since the last developer forum I was active in has been bought and pulverized by some people I've never entered a forum again for a while.

Now a year later I am confident again and hope to have found a new forum right here for now and the future.

 

 

My problem:

 

> The basic architecture

1. I'm working on a Android game project using multithreading.

2. The game has several game loops i.e. a "logic loop"

3. Every loop has it's own "unit" memory to iterate through

 

> The problem

When creating a new "unit" while the game is running (i.e. a tank was produced in a factory -> this example happens in the logic-thread/loop) I need to make the reference of the tank known to the other threads by saving the reference in their "unit memory" (a list or a set).

 

Of course this would terminate the program with an error, since you can't modify a list while at the same time iterating over it.

My first solution was to synchronize the lists and make them thread safe. This however leads to the problem that it makes first of all the whole code significantly a lot slower and the thread adding the new objects had to wait for every thread to finish iterating causing the whole game to stuck a few ms when a new unit was created.

 

Has anyone an idea how I could possibly solve this multithreading issue?

 

 

Thank you very much

- Icca

Edited by IceCave
0

Share this post


Link to post
Share on other sites

You could use a ConcurrentLinkedQueue as your list, and iterate using the iterator method. Then elements are added to directly to the thread's list, but it uses a wait-free algorithm instead of locking the whole list. You can alternatively use CopyOnWriteArrayList if adding elements is very rare.

2

Share this post


Link to post
Share on other sites

Hi! Hope you will like it here. smile.png

 

Does each thread need its own entity list in memory?

 

Can't one thread actually manage the modifiable scene graph / entity list ... and pass an immutable frameEntityList, built specifically for the next frame, to the other threads?

Guess the logic thread would have to remember or signal that a tank was built, the entity management would create the actual object for the next frame and add it to the immutable list.

 

You might even be able to add some culling when you build the frameEntityList.

 

Disclaimer: as far as I know such a central thread managing logic is not uncommon, but I am not yet a concurrency expert.

2

Share this post


Link to post
Share on other sites

You could use a ConcurrentLinkedQueue as your list, and iterate using the iterator method. Then elements are added to directly to the thread's list, but it uses a wait-free algorithm instead of locking the whole list. You can alternatively use CopyOnWriteArrayList if adding elements is very rare.

 

and @VildNinja

 

I have played around with this idea to use an "object stream". I was not aware of ConcurrentLinkedQueue which is a very interesting class in that case.

I've tried it also with a concurrent HashSet by using

Set set = Collections.newSetFromMap( new ConcurrentHashMap() );

to increase performance furthermore but I like the FIFO-Version which can become handy and looks also better in code.

Maybe will change it later at the very end of development to (Concurrent)HashSet to potentially increase performance.

 

An example abstract class showing the general architecture of one of my unit memory classes implementing the idea with a ConcurrentLinkedQueue.

public class ThreadUnitMemory< A extends AbstractObject<A>> {
	private final HashSet<A>				allObjects;
	private final ConcurrentLinkedQueue<A>	clqObjectStreamNew, clqObjectStreamKill;
	
	public LoopDatabase() {
		allObjects = new HashSet<A>();
		clqObjectStreamNew = new ConcurrentLinkedQueue<A>();
		clqObjectStreamKill = new ConcurrentLinkedQueue<A>();
	}
	
	public void addObjectToThread( A a ) {
		clqObjectStreamNew.offer( a );
	}
	
	public void removeObjectFromThread( A ao ) {
		clqObjectStreamTrash.offer( a );
	}

	private A buffer;
	
	public void loop() {
		while( !clqObjectStreamNew.isEmpty() ) {
			buffer = clqObjectStreamNew.poll();
			allObjects.add( buffer );
		}
		
		while( !clqObjectStreamTrash.isEmpty() ) {
			buffer = clqObjectStreamTrash.poll();
			allObjects.remove( buffer );
		}

		// compute all the logic stuff we are actually here for - iterating over allObjects
	}
}

Hi! Hope you will like it here. smile.png

 

Does each thread need its own entity list in memory?

[...]

 

An indeed interesting architectural solution I would really like to implement but I've decided against but will try that out someday definitly for other projects.

Reasons I decided against:

>> Needs more time to implement. Especially when you are later in development stage, I guess it would be best to implement this from the very beginning.

>> Needs lots of ressources in general which is not justified in my case. The threads are totally seperated from one another beside the little tweak that new objects have to be added to their memory when needed.

>> All threads have their individual memory architecture.

the logic-thread for example only needs a simple set of objects;

the OpenGL-thread is sorting the objects in a scene graph;

the AI-thread is sorting with different hyrachies depending on the ai's and their relation to the object;

and this goes on... again it was designed from the beginning that every thread is and works totally independent.

 

However, I've wrote this down for a later project.

 

Thank all of you very much!

- Ica

Edited by IceCave
1

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