On Wed, Sep 25, 2024 at 8:47 PM Anton Khirnov wrote:
> Quoting Nuo Mi (2024-09-25 14:37:43)
> > On Tue, Sep 24, 2024 at 11:44 PM Anton Khirnov
> wrote:
> >
> > > Quoting Nuo Mi (2024-09-24 16:56:46)
> > > > On Tue, Sep 24, 2024 at 10:43 PM Nuo Mi wrote:
> > > >
> > > > Currently, the pure decod
Quoting Nuo Mi (2024-09-25 14:37:43)
> On Tue, Sep 24, 2024 at 11:44 PM Anton Khirnov wrote:
>
> > Quoting Nuo Mi (2024-09-24 16:56:46)
> > > On Tue, Sep 24, 2024 at 10:43 PM Nuo Mi wrote:
> > >
> > > Currently, the pure decode speed for 8K is around 27–30 fps.
> > > To achieve stable 8K@30 play
On Tue, Sep 24, 2024 at 11:44 PM Anton Khirnov wrote:
> Quoting Nuo Mi (2024-09-24 16:56:46)
> > On Tue, Sep 24, 2024 at 10:43 PM Nuo Mi wrote:
> >
> > Currently, the pure decode speed for 8K is around 27–30 fps.
> > To achieve stable 8K@30 playback, we may need to go through several
> rounds
>
Quoting Nuo Mi (2024-09-24 16:56:46)
> On Tue, Sep 24, 2024 at 10:43 PM Nuo Mi wrote:
>
> Currently, the pure decode speed for 8K is around 27–30 fps.
> To achieve stable 8K@30 playback, we may need to go through several rounds
> of refactoring and optimization for both the decoder and executor,
On Tue, Sep 24, 2024 at 10:43 PM Nuo Mi wrote:
>
>
> On Tue, Sep 24, 2024 at 10:24 PM Zhao Zhili
> wrote:
>
>>
>>
>> > On Sep 24, 2024, at 22:16, Nuo Mi wrote:
>> >
>> > Due to the nature of multithreading, using a "ready check" mechanism
>> may introduce a deadlock. For example:
>> >
>> > Supp
On Tue, Sep 24, 2024 at 10:24 PM Zhao Zhili wrote:
>
>
> > On Sep 24, 2024, at 22:16, Nuo Mi wrote:
> >
> > Due to the nature of multithreading, using a "ready check" mechanism may
> introduce a deadlock. For example:
> >
> > Suppose all tasks have been submitted to the executor, and the last
>
> On Sep 24, 2024, at 22:16, Nuo Mi wrote:
>
> Due to the nature of multithreading, using a "ready check" mechanism may
> introduce a deadlock. For example:
>
> Suppose all tasks have been submitted to the executor, and the last thread
> checks the entire list and finds
> no ready tasks. It
Due to the nature of multithreading, using a "ready check" mechanism may
introduce a deadlock. For example:
Suppose all tasks have been submitted to the executor, and the last thread
checks the entire list and finds
no ready tasks. It then goes to sleep, waiting for a new task. However, for
som
