Common Package Specification (CPS) in Practice: A Full Round Trip Implementation in Conan C++ Package
Specification (CPS) in practice: A full round trip implementation in Conan C++ package manager CppCon24Outline - Introduction to Common Package Specification (CPS) - Creation of CPS files from existing existing Conan packages - Loading CPS files generated by build systems - Generating build system native files from CPS - Location of CPS files - Lessons learned and conclusions 3*ISO C++ survey 2024 Setting CI Managing CMake projects Why a Common Package Specification (CPS) 4Common Package Specification (CPS) ZLib zlib.cps 5 …Existing solutions Searching for Convergence in C++ Package Management0 码力 | 66 页 | 1.76 MB | 5 月前3Common Package Specification: Getting Build Tools to Talk to Each Other
Definition and scope - Implementation experience - CPS basics - Directories and libraries: ZLib - Components and requirements: Openssl - Full CPS - Advanced use cases - Full library definition - - Runtime - Conditionals - Editable packages - Protobuf modules and cross-building - CPS files location - Speeding adoption hints - Conclusions and next steps 3#includeint main(void){ -I /include -L /lib -lzlibCommon Package Specification (CPS): Scope ZLib CPS 7 …Related work - CPS: https://cps-org.github.io/cps by Matthew Woehlke et al - https://www.open-std.org/jtc1/sc 0 码力 | 94 页 | 1.58 MB | 5 月前3Libraries: A First Step Toward Standard C++ Dependency Management
Brown, Daniel Ruoso https://www.youtube.com/watch?v=R1E1tmeqxBYSpec: Common Packaging Specification (CPS) ● Proposed by Kitware’s Matthew Woehlke ● Presented to ISO C++ Tooling Study Group ○ https://wg21 27Momentum: Postmodern (?) CMake ● CMake support ⇒ trivial upgrades ● Replace CMake modules with CPS JSON ● Trivially adoptable for current CMake users ○ Ideally via normal CMake version upgrades ○ 28Upside: Easier CMake interop ● Build system interop and freedom! ● Generate via templated foobar.cps.in files and find/replace ○ Very common to see foobar.pc.in files now! ● JSON interop commoditized0 码力 | 82 页 | 4.21 MB | 5 月前3绕过conntrack,使用eBPF增强 IPVS优化K8s网络性能
powerful enough Performance measurement Test topology Test result Service type Short connection cps Short connection P99 latency Long connection pps ClusterIP +40% -31% not available NodePort +64% Jobs https://careers.tencent.com/home.html Bugs solved – 1/2 • IPVS conn_reuse_mode=1 low cps Ip_vs_conn nf_conn New ip_vs_conn Bugs solved – 2/2 • DNS resolution delays for 5s Iptables SNAT0 码力 | 24 页 | 1.90 MB | 1 年前3Jenkins System Information
workflowaggregator 2.5 true workflowapi 2.16 true workflowbasicsteps 2.5 true workflowcps 2.33 true workflowcpsgloballib 2.8 true workflowdurabletaskstep 2.11 true workflowjob 2.12 true workflowmultibranch0 码力 | 5 页 | 122.16 KB | 1 年前3Connecting User And Library Code
@@@ Did not make it into the standard, work was held back be the consideration of the Function CPs @@@ All of library is same namespace, user code without frame is user space2. Improvement of usage:0 码力 | 58 页 | 18.82 MB | 5 月前3TiDB v6.1 Documentation
can do: • Go to TiDB monitoring dashboard and view the request command type through Query Summary > CPS By Instance. • If COM_QUERY is replaced by COM_STMT_EXECUTE or COM_STMT_PREPARE in the re- quest, can do: • Go to TiDB monitoring dashboard and view the request command type through Query Summary > CPS By Instance. • If the number of COM_STMT_EXECUTE in the request is far more than the number of COM_STMT_PREPARE you: • Go to TiDB monitoring dashboard and view the request command type through Query Summary > CPS By Instance. • And find that cachePrepStmts=true has been configured, but COM_STMT_PREPARE �→ is0 码力 | 4487 页 | 84.44 MB | 1 年前3Go on GPU
cb.Release() ce := cb.MakeComputeCommandEncoder() ce.SetComputePipelineState(fn.funcMul.cps) ce.SetBuffer(a, 0, 0) ce.SetBuffer(b, 0, 1) ce.SetBuffer(out, 0, 2) ce.SetBuffer(dp0 码力 | 57 页 | 4.62 MB | 1 年前3TiDB v7.6 Documentation
can do: • Go to TiDB monitoring dashboard and view the request command type through Query Summary > CPS By Instance. • If COM_QUERY is replaced by COM_STMT_EXECUTE or COM_STMT_PREPARE in the re- quest, can do: • Go to TiDB monitoring dashboard and view the request command type through Query Summary > CPS By Instance. • If the number of COM_STMT_EXECUTE in the request is far more than the number of COM_STMT_PREPARE you: • Go to TiDB monitoring dashboard and view the request command type through Query Summary > CPS By Instance. • And find that cachePrepStmts=true has been configured, but COM_STMT_PREPARE �→ is0 码力 | 6123 页 | 107.24 MB | 1 年前3TiDB v8.1 Documentation
panic when the new framework for collations is disabled #52772 @wjhuang2016 • Fix the issue that the CPS by type metric displays incorrect values #52605 @nolouch 56 • Fix the issue that the nil pointer can do: • Go to TiDB monitoring dashboard and view the request command type through Query Summary > CPS By Instance. • If COM_QUERY is replaced by COM_STMT_EXECUTE or COM_STMT_PREPARE in the re- quest, can do: • Go to TiDB monitoring dashboard and view the request command type through Query Summary > CPS By Instance. • If the number of COM_STMT_EXECUTE in the request is far more than the number of COM_STMT_PREPARE0 码力 | 6479 页 | 108.61 MB | 9 月前3
共 69 条
- 1
- 2
- 3
- 4
- 5
- 6
- 7