Measure and track cuda.core import time #2045

Activity

1. leofang

   added this to the cuda.core next milestone on May 7, 2026
2. leofang

   added

   P1Medium priority - Should doMedium priority - Should do

   on May 7, 2026
3. leofang

   added a parent issue on May 7, 2026

   • Python latency testing & benchmarking #1580
4. leofang

   added

   cuda.coreEverything related to the cuda.core moduleEverything related to the cuda.core module

   performance

   on May 7, 2026
5. mdboom commented on May 7, 2026

   

   mdboom

   on May 7, 2026

   Contributor

   More actions

   Maybe @danielfrg would be interested in adding this to the benchmarking suite?

   It would be good to (1) exclude time spent getting to basic Python (python -c pass time), and also measure "time to calling first driver.init()", because that includes not just Python import, but dlopen-ing and then resolving all the symbols.

   👍React with 👍1Reacted by Leo Fang
6. mdboom

   self-assigned this

   on May 13, 2026
7. mdboom commented on May 13, 2026

   

   mdboom

   on May 13, 2026

   Contributor

   More actions

   Should merge this #2005 first before starting on this -- it would be helpful to have a cuda_core benchmark suite first.
8. mdboom

   removed their assignment

   on May 13, 2026
9. leofang

   assigned

   danielfrg

   on May 13, 2026
10. leofang

    modified the milestones: cuda.core v1.1.0, cuda.core next on Jul 7, 2026
11. leofang

    modified the milestones: cuda.core 1.2.0, cuda.core 1.3.0 on Sep 2, 2026