Skip to main content

nearorder

codecov

nearorder is an experimental project for validating search strategies on mostly ordered sequences with sparse disorder, focusing on performance stability, fallback behavior, and long-term robustness.

Key words

  • experimental / validation

  • mostly ordered

  • sparse disorder

  • performance stability / fallback

Motivation

In many real-world engineering systems, the data being queried is not fully sorted, but it is also far from being randomly disordered.

The assumptions behind this project are based on practical observations rather than theoretical worst-case models:

  • The sequence is globally monotonic (ascending or descending as a whole).

  • Disorder exists, but it is sparse and limited.

  • Disordered elements:

    • Are few in number

    • Are randomly distributed

    • Do not cluster densely within a single local interval

  • Data repair or correction is post-hoc and relatively slow.

  • Query operations are high-frequency and performance-critical.

Under these conditions, traditional binary search may fail or behave unpredictably when encountering local disorder, while linear scans are prohibitively expensive at scale.

This project does not attempt to design a universally optimal algorithm for arbitrary input.
Instead, it focuses on validating search strategies under realistic engineering assumptions, where:

  • Correctness must be preserved

  • Performance degradation must be bounded and observable

  • Long-term stability is more important than theoretical optimality

In short, this is an experiment-driven validation of a “good enough” solution under constrained, real-world disorder, rather than a general-purpose algorithmic framework.

Performance Analysis Summary

The experimental results in analysis/ and test/ consistently fall into four representative cases:

1. Sparse Random Swaps (Low Disorder, The data the author has direct access to in practice.)

Conclusion:
Performance remains stable and close to the ordered case; limited swaps do not meaningfully affect query time.

2. Block-Level Disorder

Conclusion:
Spikes occur sporadically, but the average time doesn't show a clear increase or decrease with larger block sizes; it stays mostly flat with noise.

3. Periodic Local Disorder

Conclusion: The spikes suggest specific points where performance degrades notably, likely due to alignment issues, while average performance appears stable.

4. Periodic Shuffle

Conclusion:
There's a noticeable increase in both average time and spike severity as disorder grows, peaking in intermediates before stabilizing somewhat at extremes.

Overall Observation

At the 10⁵ scale, variations caused by reasonable levels of in-sequence disorder stay within a narrow and predictable performance range, making the approach suitable for long-term operation on mostly ordered data.

Recommended Usage Pattern

For the type of data discussed above, a two-phase search strategy is recommended.

  1. Phase One: Coarse Binary Search
    Apply binary search with looser and more tolerant conditions to obtain a coarse or approximate index.
    At this stage, the goal is localization rather than exact matching.

  2. Phase Two: Window-Based Refinement
    Using the coarse index as an anchor, collect data within a bounded window and perform targeted filtering and validation inside this range.

from datetime import datetime

from nearorder.bisect import binary_search
from nearorder.filter import filter_window


def cmp(a: datetime, b: datetime) -> int:
    def datetime_to_days(dt: datetime) -> int:
        return (dt - datetime(1900, 1, 1)).days + 2

    rt = datetime_to_days(a) - datetime_to_days(b)
    return int(rt)


def cmp_precise(a: datetime, b: datetime) -> int:
    rt = a.timestamp() - b.timestamp()
    return int(rt)


index = binary_search(data, k, cmp=cmp)
assert index is not None
result = filter_window(data, k, index, window_size=24 * 4, cmp=cmp_precise)
assert len(result) > 0

What This Project Is / Is Not

This project is:

  • A validation of assumptions

  • A performance experiment

  • A reference implementation

This project is NOT:

  • A general-purpose sorting library

  • A theoretically optimal algorithm for arbitrary input

  • A drop-in replacement for standard search

License

Copyright (c) 2026 SHIINASAMA (Kaoru).

This project is released under a dual-licensing model.

It is available under the MIT License to any individual or entity, except for the organizations listed below, for whom the MIT License does not apply.

Use by the following organizations requires a separate commercial license:

  • Guangxi Guineng Power Co., Ltd.
  • Any of its affiliated, subsidiary, or related entities.

This exception is a defensive licensing measure intended solely to avoid potential conflicts related to employment-associated intellectual property or organizational use, and does not restrict general open-source usage by the public.

See DUAL-LICENSE.md for details.

Metadata

Release files for nearorder 0.1.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for nearorder 0.1.2
File Size Uploaded
nearorder-0.1.2.tar.gz 13.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for nearorder 0.1.2
File Interpreter ABI Platform
nearorder-0.1.2-py3-none-any.whl Python 3 none any Details

Total release size: 24.3 kB

Release files / nearorder-0.1.2.tar.gz

Download URL nearorder-0.1.2.tar.gz
Size 13.1 kB
Tags Source
SHA-256 checksum
How to use checksums
5fb601a22099730dc5388a7331ed9cc5685f2952dbeb1c5ab3f3804ed2cc35b3
BLAKE2b-256 checksum
How to use checksums
1cbaa1e8d6444c05d2574a16095f9d019623d3af5901d055ac717e13154ca7e6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.11.14

Release files / nearorder-0.1.2-py3-none-any.whl

Download URL nearorder-0.1.2-py3-none-any.whl
Size 11.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0f122fa004ac5e03ff9de5cab717a4f1db39fa4cc8a9fa421e98e772e1fbeec5
BLAKE2b-256 checksum
How to use checksums
12bf405bd223f1cf4e2528b97f3463b45a053c70cc42334a842c6dbfaacc0255
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/6.2.0 CPython/3.11.14

Release history Release notifications | RSS feed

This release

0.1.2 This release

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page