long total = requestsSent.get();
        if (total == 0)
            return 0.0;
        return (double) errors.get() / total;
    }

    /**
     * Get throughput in bytes per second
     *
     * @return throughput in bps
     */
    public long getThroughput() {
        long duration = System.currentTimeMillis() - establishedTime;
        if (duration == 0)
            return 0;

        try {
            Thread.sleep(10);
        } catch (InterruptedException e) {
            Thread.currentThread().interrupt();
        }

        long throughput = channelInfo.getThroughput();
        assertTrue(throughput > 0);
    }

    @Test
    void testEquals() {
        ChannelInfo other = new ChannelInfo("test-channel", mockTransport, localInterface, remoteInterface);

        }
        return totalReceiveTime.get() / (double) receives / 1000.0; // Convert to microseconds
    }

    /**
     * Calculate total throughput in MB/s based on total time
     *
     * @param totalTimeSeconds total elapsed time in seconds
     * @return throughput in MB/s
     */
    public double getThroughputMBps(double totalTimeSeconds) {
        if (totalTimeSeconds <= 0.0) {
            return 0.0;

    
    SmbFile file = new SmbFile("smb://server/share/largefile.dat", context);
    
    // Measure single channel throughput
    long singleChannelTime = measureReadTime(file, false);
    
    // Measure multi-channel throughput
    long multiChannelTime = measureReadTime(file, true);
    
    // Multi-channel should be faster

 * sum that is used for purposes such as collecting statistics, not for fine-grained synchronization
 * control. Under low update contention, the two classes have similar characteristics. But under
 * high contention, expected throughput of this class is significantly higher, at the expense of
 * higher space consumption.
 *
 * <p>This class extends {@link Number}, but does not define methods such as {@code

- Performance testing infrastructure

## Success Metrics

1. **Functional Completeness**: All features pass Windows Protocol Test Suite
2. **Performance**: 
   - Multi-channel provides >1.5x throughput improvement
   - RDMA reduces latency by >50%
3. **Reliability**: 
   - Persistent handles survive 99% of network interruptions
   - Witness protocol achieves <5 second failover time

- [ ] Test pagination and sorting
- [ ] Validate security and access control

### Testing

- [ ] Functional testing of search queries
- [ ] Performance testing (response time, throughput)
- [ ] Security testing (authentication, authorization)
- [ ] Integration testing with client applications
- [ ] User acceptance testing
- [ ] Load testing for production capacity

### Go-Live

 *       anything about how the property is tested. To find out, read the code.
 *   <li>These tests are "conformance tests", and do not attempt to test throughput, latency,
 *       scalability or other performance factors (see the separate "jtreg" tests for a set intended
 *       to check these for the most central aspects of functionality.) So, most tests use the

 * writes. The {@link Cache#cleanUp} method of the returned cache will also perform maintenance, but
 * calling it should not be necessary with a high throughput cache. Only caches built with {@link
 * #removalListener removalListener}, {@link #expireAfterWrite expireAfterWrite}, {@link
 * #expireAfterAccess expireAfterAccess}, {@link #weakKeys weakKeys}, {@link #weakValues

- Implemented scoring for DRA-backed extended resources. ([#134058](https://github.com/kubernetes/kubernetes/pull/134058), [@bart0sh](https://github.com/bart0sh)) [SIG Node, Scheduling and Testing]