[ 
https://issues.apache.org/jira/browse/SOLR-17937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18047380#comment-18047380
 ] 

Ishan Chattopadhyaya commented on SOLR-17937:
---------------------------------------------

https://github.com/apache/solr/pull/3982

This should suffice, I guess? Please review, Jan.

> Adding GPU details to the metrics API and displaying them on the Admin UI
> -------------------------------------------------------------------------
>
>                 Key: SOLR-17937
>                 URL: https://issues.apache.org/jira/browse/SOLR-17937
>             Project: Solr
>          Issue Type: Improvement
>          Components: Admin UI
>            Reporter: Puneet Ahuja
>            Assignee: Ishan Chattopadhyaya
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 10.0
>
>         Attachments: image-2025-10-03-08-22-02-032.png, 
> image-2025-11-07-17-12-59-776.png
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> GPU accelerated indexing was introduced in SOLR-17892 which enables the user 
> to leverage GPU for indexing.
> This issue proposes to add GPU metrics  to Solr's metric API . Also, add 
> these details to the admin UI for visualization. These GPU metrics include 
> name, used memory, free memory etc.
> I plan to get the GPU details to Solr via cuVS's getGPUInfo() API. If Solr is 
> started with the cuVS module enabled, this info can be obtained using a long 
> running thread that pulls this information every 5 seconds, and populating it 
> to the Metrics API.
> The CuVS getGPUinfo() API does not support getting details for multiple GPUs 
> in the system. We can just display the number of GPUs present and their 
> names, but the memory values will not be reliable in a multi-GPU setup.
>  
> !image-2025-11-07-17-12-59-776.png!



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to