On 5/26/17, Martin Vahi <martin.v...@softf1.com> wrote: > > 3) > While being at the "Home" or "Wiki" page, > select the "Files" menu option and observe > the multi-second delay. Navigating folders > at the Web based file browser is also > slightly sluggish.
That's because you have 403,890 separate files in your project. By comparison, SQLite (the project for which Fossil was designed) has 1,945 files and Fossil itself has only 1,007 files. NetBSD, which is what most people think of when you say "big project with a lot of files", has only 307,454. Sadly, I made some design decisions early on that make it difficult to scale Fossil to these kinds of massive projects. I've been kicking around a new idea lately: "Fit" which is a combination of "Fossil" and "Git". Basically, it uses Git's hierarchical low-level file structure artifact format but with Fossil's UI and implementation. Such a design would scale better to projects with many hundreds of thousands of files. And it would be able to push and pull with legacy Git clients for collaboration. All the while retaining the ease of use, rich interface, and module design that most people like about Fossil. A key design requirement for "Fit" is that when you import from Fossil, it remembers all of the legacy Fossil hash identifiers and uses those as aliases for the new Fit/Git hashes, so that references to Fossil hash names continue to work. Also, the Git file structure would need to be extended to support tickets and wiki and named branches and a few other details like that, but all of that should be easy to do. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
