Skip to content

issues Search Results · repo:tracker1/queue-testing language:JavaScript

Filter by

3 results  (85 ms)

3 results

intracker1/queue-testing (press backspace or delete to remove)

tracker1/queue-testing
In the SplicingQueue you could use shift instead of splice

Shift should be faster then splice maybe add ShiftingQueue to the pull instead of changing the SplicingQueue Also all the Queues that uses undefined should rest when the Queue is empty.
  • barak007
  • Opened 
    on Mar 24, 2021
  • #3

tracker1/queue-testing
Results

Hey, I have prepare a test.sh script to bring results here: #!/usr/bin/env bash FIRST_TRY=10000 SECOND_TRY=100000 QUEUES=(SplicingQueue DeletingQueue UndefinedQueue MapQueue MapUndefQueue) for QUEUE ...
  • cojack
  • Opened 
    on Mar 23, 2021
  • #2

tracker1/queue-testing
Do the `DeletingQueue` and `UndefinedQueue` become faster when the base object is an object with `null` prototype, rather than `{}`?

I might bother to test what happens if you initialize the queues as Object.create(null) instead of {}.
  • lewisje
  • Opened 
    on Mar 22, 2021
  • #1
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! Restrict your search to the title by using the in:title qualifier.