}

        try {
            dataIndexHelper.crawl("test-session-force-stop");
            assertTrue("Should exit quickly when force stopped", true);
        } catch (Exception e) {
            assertTrue("Force stop should handle exceptions quickly", true);
        }
    }

    public void test_crawl_with_short_intervals() {
        try {
            // Test with minimal interval

        verify(mockContext, atLeastOnce()).getConfig();
    }

    @Test
    @DisplayName("Should handle invalid NetBIOS name quickly")
    @Timeout(value = 1, unit = TimeUnit.SECONDS) // Very short timeout
    void testGetNbtByNameInvalid() {
        // When/Then - Should fail quickly with invalid characters
        assertThrows(Exception.class, () -> {
            nameServiceClient.getNbtByName("INVALID@#$%NAME");

        System.out.printf("Overall Performance Test: completed in %.2f ms%n", totalTimeMs);

        // Should complete very quickly with all optimizations
        assertTrue(totalTimeMs < 100, "All operations should complete quickly with performance fixes");

        pool.close();
    }

        assertTrue(end - start < 50); // Should return quickly

        // Test with rule that has no delay
        helper.addIntervalRule("01:30", "15:15", "*", 0);
        start = System.currentTimeMillis();
        helper.delayByRules();
        end = System.currentTimeMillis();
        assertTrue(end - start < 50); // Should return quickly

    }

    @Test
    @DisplayName("EmptyIterator should be lightweight and efficient")
    void testPerformanceCharacteristics() {
        // When - create many instances quickly
        long startTime = System.currentTimeMillis();

        for (int i = 0; i < 10000; i++) {
            EmptyIterator iterator = new EmptyIterator();
            iterator.hasNext();
            iterator.next();

            assertNotNull(jobProcess2);
            // Since echo command completes quickly, processes might already be finished
            // So we just verify that processes were created without errors

            Set<String> sessionIds = processHelper.getRunningSessionIdSet();
            // Since echo commands complete quickly, we may not catch them running
            // Just verify no exceptions occurred

    * You can normally quickly detect it by going to the "Files changed" tab in the PR and checking if the updated file(s) starts with `docs/en/docs`. The original version of the docs is always in English, so in `docs/en/docs`.
* `lang-all`: Translations

            long startTime = System.nanoTime();
            info.decode(largeBuffer, 0, 24);
            long endTime = System.nanoTime();

            // Should complete quickly (under 1ms)
            assertTrue((endTime - startTime) < 1_000_000);
        }

        @ParameterizedTest
        @ValueSource(ints = { 24, 32, 100, 1000, 10000 })

 *
 * <p>Lookups by row key are often faster than lookups by column key, because the data is stored in
 * a {@code Map<R, Map<C, V>>}. A method call like {@code column(columnKey).get(rowKey)} still runs
 * quickly, since the row key is provided. However, {@code column(columnKey).size()} takes longer,
 * since an iteration across all row keys occurs.
 *
 * <p>Because a {@code TreeBasedTable} has unique sorted values for a given row, both {@code

 *
 * <p>Lookups by row key are often faster than lookups by column key, because the data is stored in
 * a {@code Map<R, Map<C, V>>}. A method call like {@code column(columnKey).get(rowKey)} still runs
 * quickly, since the row key is provided. However, {@code column(columnKey).size()} takes longer,
 * since an iteration across all row keys occurs.
 *
 * <p>Because a {@code TreeBasedTable} has unique sorted values for a given row, both {@code