Started by GitHub push by Geolykt4a61527c43882597731c878094708d8953c9ee0eaa61527c43882597731c878094708d8953c9ee0earefs/remotes/origin/mastera61527c43882597731c878094708d8953c9ee0eaa61527c43882597731c878094708d8953c9ee0earefs/remotes/origin/mastera61527c43882597731c878094708d8953c9ee0eaa61527c43882597731c878094708d8953c9ee0earefs/remotes/origin/masterhttps://github.com/Geolykt/FastStar.githttps://stianloader.org/jenkins/job/faststar/4/artifacthttps://stianloader.org/jenkins/job/faststar/changeshttps://stianloader.org/jenkins/job/faststar/4/https://stianloader.org/jenkins/job/faststar/4/testReportfalse#47757689791faststar #44falsefalse499SUCCESS1721318819675https://stianloader.org/jenkins/job/faststar/4/.gitignoresrc/main/resources/fastmixins.jsonsrc/main/java/de/geolykt/faststar/mixin/FastEmploymentAgencyMixins.javagradle.propertiesbuild.gradlea61527c43882597731c878094708d8953c9ee0ea1721317924000https://stianloader.org/jenkins/user/geolyktGeolyktadmin@geolykt.deOnly consider a small subset of people when trying to find a replacement for a job Let's not do a stellaris, yeah? Also, the main bottleneck now are our knn queries. From the looks of it they still consume far too much of our previous CPU time. So it's quite clear that we'd probably need to get rid of the Spatial Query Arrays and use a library. Perhaps we are back to tinspin-indexes? Although I don't expect too much from it so maybe just go completely ballistic and use a native library for this? 2024-07-18 17:52:04 +0200a61527c43882597731c878094708d8953c9ee0eaOnly consider a small subset of people when trying to find a replacement for a jobedit.gitignoreeditsrc/main/resources/fastmixins.jsoneditgradle.propertieseditbuild.gradleaddsrc/main/java/de/geolykt/faststar/mixin/FastEmploymentAgencyMixins.javagithttps://stianloader.org/jenkins/user/geolyktGeolyktgeolykt