pgdbf
mammoth
pgdbf | mammoth | |
---|---|---|
3 | 43 | |
137 | 872 | |
- | - | |
0.0 | 0.0 | |
almost 4 years ago | 12 months ago | |
M4 | Java | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pgdbf
-
FoxPro: Interview with Wayne Ratliff
My Internet claim to fame was writing a program to get people off of FoxPro to PostgreSQL: https://github.com/kstrauser/pgdbf
FoxPro was nifty in many ways, but nightmarish outside the “single person running the app with the database on their local hard drive” setup. The moment you tried to put the database files on a file share (which is how you used it as a network DB), it was a world of locking pain. And a fun fact: the client libraries were single threaded to the point that you could only run one query at a time per machine. If you had 2 apps running at once, only one of them could be querying at any given time.
-
Show HN: Write universally accessible SQL, not library-specific ORM wrapper APIs
Sigh, if only. OK, so the rest of the story was that the original app was written in Visual FoxPro. I was hired to build a web frontend for it. Well, turns out 1) there is, or at least was, no native VFP client for Unix, and 2) the Windows client was single threaded per host, so you couldn't even farm the connectivity out to a Windows process. After struggling with this for a while -- a cluster of Win XP hosts running a single-threaded VFP client and serving results to a Linux webserver via XMLRPC, as was the custom at the time -- I finally said "screw this, let's brute force it." That turned into https://github.com/kstrauser/pgdbf, which is an app to convert a VFP table into a PostgreSQL table. We had it running on a cron job, which worked fine because the website was read-only and it was the VFP app that was actually writing to the tables. It was alright to have up to a few hours of latency between the VFP view of the data and the PostgreSQL view of it.
When the company later committed to rewriting the VFP app in a sane language, they wrote it to run directly against PostgreSQL. That was quite a few years after I'd started there, though.
-
Microsoft's FoxPro 2.5 Is Fast and Easy to Use (1993)
By orders of magnitude, my most popular open source release was a project to help people migrate from FoxPro to PostgreSQL: https://github.com/kstrauser/pgdbf
FoxPro was cool for desktop apps, but couldn’t make the leap to networked clients, where “networked” was more than “has access to the file share where the database files live”.
In the early 2000s I was hired to write a website that published reports from data stored in a Visual FoxPro database. A not-so-fun fact I learned: the VFP database libraries are single-threaded at the OS level. That is, you couldn’t run more than one query on the same machine at the same time, even in different processes. One would block until another finished. In a fit a panic and madness, I ended up writing an XMLRPC service (“which was the style at the time”) in Python, deploying it to multiple old Windows XP desktops we had laying around, and writing a database adapter for the web server that would send queries to those servers round-robin. Need more parallelism? Add another Windows XP box running my janky little service. It was awful, but it let us ship the project.
Later I wrote pgdbf so that we could run a cron job that would copy all our data out of FoxPro into PostgreSQL so that I could code against a real multi-user database that was vastly better in every way. By accident, I released it at a time when the world was wondering how they were going to migrate from FoxPro to something else. Turns out VFP was wildly popular in South America, and pgdbf turned out to be wildly popular there too, which let to me getting lots of email in Spanish and Portuguese and offers to come talk at user groups. I turned those down because what was I gonna say, “yeah, it was painful for me, too. Anyway, here you go and good luck!”?
mammoth
- Is 48GB enough
-
Run one server on two machines
But maybe soon?
-
The server software iceberg
Yes
-
Best 1.8 .jar for Hunger Games
80 is a ton of players though, you might be able to get away with it as long as you have very powerful hardware. This might get better in the future if Mammoth "Seamless" mode gets stable.
-
Can't believe I'm still playing this game after 10 years.
There really isn't a networking library that is available that a new planetside server could use. I think spatialOS had a lot of hype around it back in 2018, but for various reasons its not widely used. There was a recent project that hypothetically could handle the scale of planetside 2 with good performance, but its still in the very early stages, and probably will be for a long while.
-
Is it possible to merge two servers into one instance?
Possible? Sure. WorldQL's Mammoth should be able to accomplish this, though it's still very much in development https://github.com/WorldQL/mammoth. Seems to be far from ready for actual server use.
-
How do servers with large (140+) player counts maintain playable TPS?
After a quick google, it looks like WorldQL and Mammoth may be what you want. They say (and show, actually) they've tested it with up to 1000 players over multiple servers (on a single world) and kept a solid 20 TPS.
- This server software was able to get 1000+ players running on one Minecraft world at once without server lag and has recently released a public build. I posted it as a suggestion in the regular subreddit but it immediately got taken down.
- This server software was able to get 1000+ players running on one Minecraft world at once without server lag and has recently released a public build. Please add this housemaster so we don't have too wait through a large queue and can have even more players on the server at once.
- This project looks insane but idk if its actually realistic. What do you guys think?
What are some alternatives?
dabo - Dabo: A Framework for developing data-driven business applications
MultiPaper - Multi-server, single-world papermc implementation
Norm - The SQL generation library you already know how to use.
MotorMC - MotorMC is a blazing fast, multi threaded, asynchronous Minecraft server software that aims to handle many players (1000+) on a single world while still providing an experience as close to vanilla Minecraft as possible.
ui-editor - A collaboration tool for engineering teams. Working concept for design tool that can generate readable code. Aimed to replace modern bloatware like jira, slack, outlook, IDE, and redundant work. A developer tool built by developer to make designers do the developer's work.
minecraft-optimization - Minecraft server optimization guide
rusqlite-model - Model trait and derive implementation for rusqlite
Glowstone - A fast, customizable and compatible open source server for Minecraft: Java Edition
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
FarPlaneTwo - Level-of-Detail renderer in Minecraft. Allows for render distances of millions of blocks. (Cubic Chunks-compatible) (WIP)
pure-orm - A pure ORM for writing native SQL queries yielding pure business objects
worldql_server - The spatial message broker and database for real-time multiplayer experiences. Official Rust implementation.