Lab 7 do oceny #9
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
ok |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Żeby thread mogło przyjąć obiekt Simulation, to klasa
simulation musi implementować interfejs Runnable
runSync dobrze generowało opis i mapę pojedynczo, a wersja
asynchroniczna działa współbieżnie
wersja asynchroniczna miesza generowanie opisu i mapy z kilku wątków na raz podczas wypisywania, ponieważ kilka wątków na raz chce modyfikować mapę i uzywa ConsoleDisplayMap w swoim czasie, nie czekając aż inne wątki skończą dany ruch.
Tworzenie dużej ilosci wątków jest bardzo kosztowne, więc korzystanie z thread poola i ograniczonej liczby wątków jest szybsze niż podejście 1 wątek - 1 symulacja.
Wesołych świąt!