On 5/26/17, Richard Hipp wrote:
>
> Sadly, I made some design decisions early on that make it difficult to
> scale Fossil to these kinds of massive projects.
>
On the other hand, I also made some good design choices, such as the
use of SQLite for storage. And it occurred to me
On 5/26/17, Martin Vahi 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
Reproduction:
1)
Open the link behind the "Home" menu option, the page page at
https://www.softf1.com/cgi-bin/tree1/technology/flaws/mmmv_parasail_projects.bash/home
2)
Select the "Wiki" menu option and observe that
the site is "lightning fast", the new page
is displayed practically the
Zakero:
> Did you check the execution time of the "find | sort" versus the
> "listfossil()"? Looking at your script, I think you can simplify it
> a bit.
The script takes between 1.2 and 1.8 seconds in the original form, and
between 130 and 160 ms if the `listfossil()' function is simplified to
Hello Florian,
Did you check the execution time of the "find | sort" versus the
"listfossil()"? Looking at your script, I think you can simplify it a bit.
# Pass all Repositories and output their name and description
fossil_info()
{
for REPO in $@
do
echo $(basename "$REPO")
fossil
On another server, where I have access to PHP, it also takes less than
100 ms to query the repository files using the built-in PDO/sqlite
interface.
So it seems that running ./sqlite3 instead of ./fossil could speed up
the queries.
--Florian
___
Thank you very much for the quick fix, it also works fine on my system.
--Florian
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On 5/26/17, Florian Balmer wrote:
>
> For 10-20 repositories, the following (skeleton) shell script takes
> more than 1 second to finish:
>
> #!/bin/sh
> ...
> listfossil() {
> echo "$(basename "$1")"
> cat <<'SQL' | ./fossil sql --repository "$1"
> SELECT value
On 5/26/17, Florian Balmer wrote:
> On Windows, the Fossil `--skin LABEL' command line option can't be
> used to load a custom skin from a subdirectory, probably because only
> skin labels containing forward slashes but not backslashes are treated
> as paths to
El 26/05/2017 a las 09:44, Florian Balmer escribió:
> I would highly appreciate a configuration option (similar to
> `index-page') to set custom default timeline query parameters.
+1
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
I'm using a customized repository index page to display a link to each
repository, along with the project name and description queried
directly from the repository database files.
For 10-20 repositories, the following (skeleton) shell script takes
more than 1 second to finish:
#!/bin/sh
...
On Windows, the Fossil `--skin LABEL' command line option can't be
used to load a custom skin from a subdirectory, probably because only
skin labels containing forward slashes but not backslashes are treated
as paths to subdirectories containing the skin files:
12 matches
Mail list logo