microsoft / microsoft/WindowsAppSDK

LanguageModel.GetReadyState() takes 20 to over 100 seconds to run on Intel

Open
#5,487 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-WCR
Dominant language
C++
Stars
4.7k
Forks
471
Avg merge
3d 13h
Merged PRs (30d)
28

Description

Describe the bug

I've filed feedback https://aka.ms/AAwhb0j -- but in case anyone knows if this is an easily fixable problem.

i have a new surface laptop for business 7 and using Phi Silica is really sluggish to start up. this is seen in the AI Dev Gallery (just trying to start a text generation task -- AI APIs --> click Phi Silica, and it looks like it is stuck) and using the exported Phi Silica solution, untouched except for adding a stopwatch.

running it three times, it's taken ~110 seconds, ~20 seconds, and ~60 seconds.

Steps to reproduce the bug
    var stopwatch = Stopwatch.StartNew();
    var readyState = LanguageModel.GetReadyState();
    stopwatch.Stop();
    Debug.WriteLine($"LanguageModel.GetReadyState() took {stopwatch.ElapsedMilliseconds} ms");
Expected behavior

No response

Screenshots

No response

NuGet package version

None

Packaging type

No response

Windows version

No response

IDE

No response

Additional context

WindowsAppSDK 1.8experimental2, Windows build 26120.4161, no more updates available in Windows Update

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported LanguageModel.GetReadyState() call with Phi Silica on the stated Surface Laptop and WindowsAppSDK 1.8experimental2 environment, using the stopwatch shown in the issue. Review the linked feedback and compare repeated timings; done requires identifying a confirmed cause or actionable fix for the startup delay.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
ai, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.