Description

Adds a new C# solution. This is based off of the C# solution_2, with one main difference. It uses a bool[] instead of a ulong[]. This will result in 8-bit flags instead of 1-bit, but it means we don't need to do math manually, can use IndexOf on the array to find the next unmarked slot, and can more easily slice and follow patterns friendly to avoiding bounds checking.

Contributing requirements

• [X] I read the contribution guidelines in CONTRIBUTING.md.
• [X] I placed my solution in the correct solution folder.
• [X] I added a README.md with the right badge(s).
• [X] I added a Dockerfile that builds and runs my solution.
• [X] I selected drag-race as the target branch.
• [X] All code herein is licensed compatible with BSD-3.

Description

Contributing requirements

• [ x] I read the contribution guidelines in CONTRIBUTING.md.
• [x ] I placed my solution in the correct solution folder.
• [x ] I added a README.md with the right badge(s).
• [x ] I added a Dockerfile that builds and runs my solution.
• [x ] I selected drag-race as the target branch.
• [x ] All code herein is licensed compatible with BSD-3.

new sieve implementation maybe. i don't know if this is really new implementation i just got this idea and it gave me good result on my pc when I run it. 👍hope you like it

Description

Contributing requirements

• [ ] I read the contribution guidelines in CONTRIBUTING.md.
• [ ] I placed my solution in the correct solution folder.
• [ ] I added a README.md with the right badge(s).
• [ ] I added a Dockerfile that builds and runs my solution.
• [ ] I selected drag-race as the target branch.
• [ ] All code herein is licensed compatible with BSD-3.

Description

This PR includes a ckermit implementation of a prime sieve, it outputs like q3w3e3;1;75;algorithm=base,faithful=no when the image created by the dockerfile is run.

The implementation is a very very small edit on my kermitSieve

Contributing requirements

• [x] I read the contribution guidelines in CONTRIBUTING.md.
• [x] I placed my solution in the correct solution folder.
• [x] I added a README.md with the right badge(s).
• [x] I added a Dockerfile that builds and runs my solution.
• [x] I selected drag-race as the target branch.
• [x] All code herein is licensed compatible with BSD-3.

Description

Disables seccomp when running docker.

For unknown reasons, running python under docker can be over 50% slower than native usage. This is a performance bug in docker, which has something to do with its use of seccomp. See https://pythonspeed.com/articles/docker-performance-overhead/ and the corresponding docker issue https://github.com/moby/moby/issues/41389

The performance difference is clear - locally when running make DIRECTORY=PrimePython, on a linux system the performance of the ssovtest solution goes from 1998 passes to 4110. It seems seccomp doesn't affect the usage of the external numpy library or compiled languages, but you may see a speed boost for some other interpreted languages with this fix.

Other considerations

Should we disable seccomp if it's providing security? Well, if all code in this repo has been reviewed and verified, it should be absolutely fine (note all the containers are running as root user anyway, so we better hope this is the case).

Contributing requirements

• [x] I read the contribution guidelines in CONTRIBUTING.md.
• [x] I placed my solution in the correct solution folder.
• [x] I added a README.md with the right badge(s).
• [x] I added a Dockerfile that builds and runs my solution.
• [x] I selected drag-race as the target branch.
• [x] All code herein is licensed compatible with BSD-3.

This addresses the review comments in PlummersSoftwareLLC#489 (zero-initialization of the ArrayPool buffer, and switching to UInt32 elements). I've also removed some unnecessary variables.

On my machine, these changes increase the number of passes from 2906 for the version currently in the main tree, to 6977 for this version.

Description

Implements Numba and Numpy effectively to give the sieve a 10% to 20% boost in performance over solution 3

Contributing requirements

• [x] I read the contribution guidelines in CONTRIBUTING.md.
• [x] I placed my solution in the correct solution folder.
• [x] I added a README.md with the right badge(s).
• [x] I added a Dockerfile that builds and runs my solution.
• [x] I selected drag-race as the target branch.
• [x] All code herein is licensed compatible with BSD-3.

Description

This code has a very simple structure (46 rows, non object oriented). It uses two external libraries but has a working docker file. It is approx. 1.5 times faster than solution_3.

Contributing requirements

• [x] I read the contribution guidelines in CONTRIBUTING.md.
• [x] I placed my solution in the correct solution folder.
• [x] I added a README.md with the right badge(s).
• [x] I added a Dockerfile that builds and runs my solution.
• [x] I selected drag-race as the target branch.
• [x] All code herein is licensed compatible with BSD-3.