Thread.Sleep чем не угодил?

Question

pro.jvm

Cavidan Shestakov

Thread.Sleep чем не угодил?

#backend #java #programming #russian

0

13.04.2021

5 ответов

8 просмотров

Cavidan Shestakov Автор вопроса

Shoxrux
Чет опасно(

чем опасно?

0

13.04.2021

Shoxrux

Cavidan Shestakov
чем опасно?

Thread.Sleep has its use: simulating lengthy operations while testing/debugging on an MTA thread. In .NET there's no other reason to use it. Thread.Sleep(n) means block the current thread for at least the number of timeslices (or thread quantums) that can occur within n milliseconds. The length of a timeslice is different on different versions/types of Windows and different processors and generally ranges from 15 to 30 milliseconds. This means the thread is almost guaranteed to block for more than n milliseconds. The likelihood that your thread will re-awaken exactly after n milliseconds is about as impossible as impossible can be. So, Thread.Sleep is pointless for timing. Threads are a limited resource, they take approximately 200,000 cycles to create and about 100,000 cycles to destroy. By default they reserve 1 megabyte of virtual memory for its stack and use 2,000-8,000 cycles for each context switch. This makes any waiting thread a huge waste.

0

13.04.2021

Cavidan Shestakov Автор вопроса

Shoxrux
Thread.Sleep has its use: simulating lengthy opera...

в вашем случае ничего "опасного" в использовании thread sleep не вижу

0

13.04.2021

Shoxrux

Cavidan Shestakov
в вашем случае ничего "опасного" в использовании t...

Да в принципе вы правы

0

13.04.2021