npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

symphony-task

v1.0.0

Published

Split a day into 2880 cells then step each cell and run job in it.

Downloads

3

Readme

symphony

scheduler Stepper

Idea

A way to reduce the cost of calculating nexttime of all jobs.

Before:

Use SQL, may be SELECT JobId, JobName, JobNextTime, JobAction, IsFinished from Jobs where JobNextTime < 123456789 and JobNextTime > 12345, to find all jobs those need to run EVERY STEP (calculate all nexttime in database every step.).

Then ask worker to execute the jobs.

Now:

Use SQL too, but cache the job into a STEPs Calendar.

For example: 30 second per Step:

0 : Job1, Job2, Job3, Job4...
30: Job5, Job10 ...
60: Job6, Job7 ...
90:
120: Job8...

when the STEP on an index, then execute the jobs in Calendar, No need to run SQL EVERY STEP.

BUT! the Jobs Updating in DATABASE must be synced to the Calendar.

However, Use the Memory to exchange CPU (Maybe include Network IO/DataBase Memory/DataBase Space).