I have some questions : 1- what parts of go are

Question

I have some questions : 1- what parts of go are

thread safe and what parts are not? (from parts I mean for example map , ...)

2-when to use mutexes ?
and when to use channels ?

3-what is select statement and it's usecases?

4- can we understand that code has coroutines conflicts without running go race detector command?

0

25.06.2021

16 ответов

5 просмотров

Masoud Автор вопроса

Ludovic 'Archivist' Lagouardette
1. Most things are not thread safe, if the doc doe...

2- which one is better for performance and memory usage between mutex and channel? 4- I meant for example when we using a library we don't know how that library implemented (thread-safe or not) unless read the whole library code

0

25.06.2021

Ludovic 'Archivist' Lagouardette

Masoud
2- which one is better for performance and memory ...

2. generally the channel is better in its worst case and the mutex is better in its best case. This means that channels basically scale better in terms of accesses than mutexes 4. Read the doc. If the docs of a library don't say something is thread safe, it is generally advised to take it for not thread safe

0

25.06.2021

Roman Sharkov

1. pretty much nothing. You have to synchronize explicitly most of the time 2. when you've got mutable state shared across goroutines 3. oh, come on, you didn't pass The Tour of Go, did you? 4. no.

0

25.06.2021

Masoud Автор вопроса

Ludovic 'Archivist' Lagouardette
2. generally the channel is better in its worst ca...

thanks 😊👍🏻

0

25.06.2021

Roman Sharkov

Ludovic 'Archivist' Lagouardette
1. Most things are not thread safe, if the doc doe...

channels don't make sense when what you've got is shared state. channels are for inter-goroutine communication

0

25.06.2021

Ludovic 'Archivist' Lagouardette

Roman Sharkov
channels don't make sense when what you've got is ...

That is the kind of moments when using goroutines as agents helps

0

25.06.2021

Roman Sharkov

Masoud
2- which one is better for performance and memory ...

a mutex is always way cheaper than a channel

0

25.06.2021

Ludovic 'Archivist' Lagouardette

Roman Sharkov
a mutex is always way cheaper than a channel

afaik, failing to lock a mutex is fairly expensive

0

25.06.2021

Roman Sharkov

Ludovic 'Archivist' Lagouardette
2. generally the channel is better in its worst ca...

channels scale better? how so and why?

0

25.06.2021

Masoud Автор вопроса

Roman Sharkov
1. pretty much nothing. You have to synchronize ex...

and thank you Mr.Sharkov 😊 btw your "sched" was cool

0

25.06.2021

Roman Sharkov

Ludovic 'Archivist' Lagouardette
That is the kind of moments when using goroutines ...

it can help in some cases, but it's always going to be wasted performance sometimes a mutex is just simpler and cheaper

0

25.06.2021

Roman Sharkov

Ludovic 'Archivist' Lagouardette
afaik, failing to lock a mutex is fairly expensive

a channel is built upon multiple mutexes. It's always more expensive than a mutex

0

25.06.2021

Roman Sharkov

Masoud
and thank you Mr.Sharkov 😊 btw your "sched" was co...

u r welcome

0

25.06.2021

Ludovic 'Archivist' Lagouardette

Roman Sharkov
a channel is built upon multiple mutexes. It's alw...

No the channel implementation of go does not actually use mutexes

0

25.06.2021

Roman Sharkov

Ludovic 'Archivist' Lagouardette
No the channel implementation of go does not actua...

https://github.com/golang/go/blob/master/src/runtime/chan.go

0

25.06.2021

Ludovic 'Archivist' Lagouardette · Accepted Answer

1. Most things are not thread safe, if the doc doesn't say thread safe it is not 2. Try not to use mutexes. Also I don't like the name, bottlenecks is a far better name. Use channels instead wherever possible 3. Select waits (yields) until data is available or a condition is met. This is very useful when a coroutine must wait for several events 4. Yes, it will require quite an understanding of how go scheduling and coroutine system works

Похожие чаты

I have some questions : 1- what parts of go are

16 ответов

Похожие вопросы