On 12/22/17, John P. Rouillard wrote:
>
> Well since reverse proxy servers use a client idle setting, would I be
> crazy to suggest the same for fossil?
>
I did a half-baked idle timer in the latest check-in, using the
--max-latency option.
fossil server
The latest trunk check-in on Fossil
(http://www4.fossil-scm.org/info/05ec15cad53e8176) should do a much
better job of handling load from "fossil server". Please compile and
run it and let me know what happens.
The www4.fossil-scm.org server is running as follows:
/usr/local/bin/fossil
Hi Richard:
In message
On 12/22/17, Olivier R. wrote:
>
> There is now more than 24 subprocesses of Fossil running, and it’s
> getting really slow.
Are you saying that these 24 Fossils are spinning - using CPU cycles -
not just hung waiting on I/O?
--
D. Richard Hipp
d...@sqlite.org
On Dec 21, 2017, at 4:03 PM, Warren Young wrote:
>
> I’d recommend designing three distinct black-filled SVG icons
Another idea: Unicode may have characters you can use as icons.
Lock: http://www.fileformat.info/info/unicode/char/1f512/
Open:
Le 19/12/2017 à 21:49, Warren Young a écrit :
If it’s a sign of a bug, then it means something very bad has
happened, like the network stack has lost track of its client
somehow. To see that, you’d need to do a network capture on that
fossil instance’s network sockets. Use netstat -nap or
On Dec 22, 2017, at 7:46 AM, Olivier R. wrote:
>
> Le 19/12/2017 à 21:49, Warren Young a écrit :
>
>> If it’s a sign of a bug, then it means something very bad has
>> happened, like the network stack has lost track of its client
>> somehow. To see that, you’d need to do a
On Dec 21, 2017, at 4:57 PM, jungle Boogie wrote:
>
> On 21 December 2017 at 15:03, Warren Young wrote:
>> On Dec 21, 2017, at 2:58 PM, jungle Boogie wrote:
>>> perhaps left of the username.
>>
>> I think right, simply
On Dec 22, 2017, at 8:10 AM, Warren Young wrote:
>
> $ sudo tshark -b duration:1 port 8080 and tcp.flags.syn==1 | wc -l
Sorry, that’s bogus. Try this instead:
$ sudo tshark -i enp3s0 -w x.pcap -b duration:5 -a files:1 \
port 8080 and "tcp[tcpflags] & tcp-syn !=
On Dec 22, 2017, at 8:24 AM, Olivier R. wrote:
>
> I’ll have to kill all these processes soon and relaunch Fossil.
> I’ll do it when you think you have enough information about this problem.
My request for connection rates doesn’t require that you keep Fossil running —
in
On 12/22/17, Olivier R. wrote:
>
> I’ll have to kill all these processes soon and relaunch Fossil.
> I’ll do it when you think you have enough information about this
> problem. I’ll use Fossil 2.4 next time.
>
Maybe there is some kind of issue in the HTTP server
On 12/22/17, Olivier R. wrote:
>
> I didn’t use Fossil 2.3 because the SQLite version bundled was in beta
> stage.
That is NOT a good reason to reject the use of Fossil 2.3.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users
Hello all:
In message
Le 22/12/2017 à 16:10, Warren Young a écrit :
1. Your repo is public-facing. Is this a reasonable number of
clients to be connected at any given time to this repo? It seems
high to me, given the transient nature of most Fossil connections.
Only two devs have the right to modify the online
Le 22/12/2017 à 15:59, Richard Hipp a écrit :
On 12/22/17, Olivier R. wrote:
There is now more than 24 subprocesses of Fossil running, and it’s
getting really slow.
Are you saying that these 24 Fossils are spinning - using CPU cycles -
not just hung waiting on I/O?
On Dec 22, 2017, at 8:56 AM, Richard Hipp wrote:
>
> (afaik) nobody uses "fossil server"
> for long-running websites.
I do. Mine stay running for months at a time, including public-facing ones.
> use the xinetd/inetd style of invoking Fossil
I can only see that helping if
On Dec 22, 2017, at 10:20 AM, Olivier R. wrote:
>
> Le 22/12/2017 à 16:10, Warren Young a écrit :
>
>> 1. Your repo is public-facing. Is this a reasonable number of
>> clients to be connected at any given time to this repo? It seems
>> high to me, given the transient
On Dec 22, 2017, at 10:53 AM, Tomek Kott wrote:
>
> FWIW I also run in server mode constantly because its easy. My users (there
> are 10, they probably hit the server in bursts of 10 times one one day of the
> week) occasionally notice slowdowns and ping me.
When I
FWIW I also run in server mode constantly because its easy. My users (there are
10, they probably hit the server in bursts of 10 times one one day of the week)
occasionally notice slowdowns and ping me. This is for an internal site only,
no public facing, so shouldn't be huge numbers of users.
On Dec 22, 2017, at 11:31 AM, Warren Young wrote:
>
> I posted a long HOWTO about it back in June of 2016:
>
> https://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg23320.html
I just realized that that message is a reply to my post, not the post itself.
On Dec 22, 2017, at 9:03 AM, Warren Young wrote:
>
> Olivier, what about memory usage for the Fossil processes? “top” can give
> you this.
I just checked my public server, and each of the 4 Fossil instances is taking
about 20 MB of VM, of which only about 800 kB is
Le 22/12/2017 à 21:34, Richard Hipp a écrit :
On 12/22/17, Olivier R. wrote:
I also run Fossil on a cheap VPS.
https://www.scaleway.com/virtual-cloud-servers/
(The starter version at €2.99/month)
I'm building up a new Fossil server on this VPS now - on an ARM64-2G
On Fri 22 Dec 2017 6:13 AM, Warren Young wrote:
> On Dec 21, 2017, at 4:57 PM, jungle Boogie wrote:
> >
> > On 21 December 2017 at 15:03, Warren Young wrote:
> >> On Dec 21, 2017, at 2:58 PM, jungle Boogie wrote:
> >>>
On Thu 21 Dec 2017 11:46 AM, Dominique Devienne wrote:
>
> Nice tip.
>
> Since I've seen DRH ask about available features on GitHub since I started
> lurking on this list recently,
> I'd mention the graphs the latter provide which I find useful, in the
> Insights tab of a project.
> The Code
On 12/22/17, Olivier R. wrote:
>
> I also run Fossil on a cheap VPS.
Maybe you have used up your bandwidth quota and the ISP is throttling
your connection?
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
Le 22/12/2017 à 22:39, Richard Hipp a écrit :
On 12/22/17, Olivier R. wrote:
I also run Fossil on a cheap VPS.
Maybe you have used up your bandwidth quota and the ISP is throttling
your connection?
There is no bandwidth quota.
And when I kill the processes and
Le 22/12/2017 à 19:57, Warren Young a écrit :
On Dec 22, 2017, at 9:03 AM, Warren Young
wrote:
Olivier, what about memory usage for the Fossil processes? “top”
can give you this.
I just checked my public server, and each of the 4 Fossil instances
is taking about 20 MB
Le 22/12/2017 à 18:41, Warren Young a écrit :
I’ve added the user to the “wireshark” group, but it doesn’t work.
You have to log out and back in before group changes will take
effect.
That’s what I did. But it didn’t work.
So I used `lsof -i:8080` again.
Here is the difference with the
On 12/22/17, Olivier R. wrote:
>
> I also run Fossil on a cheap VPS.
> https://www.scaleway.com/virtual-cloud-servers/
> (The starter version at €2.99/month)
>
I'm building up a new Fossil server on this VPS now - on an ARM64-2G
machine in Paris. It is slow-going.
On 12/22/17, Richard Hipp wrote:
> On 12/22/17, Olivier R. wrote:
>>
>> I also run Fossil on a cheap VPS.
>> https://www.scaleway.com/virtual-cloud-servers/
>> (The starter version at €2.99/month)
>>
>
> I'm building up a new Fossil server on this VPS now
In message ,
Warren Young writes:
>On Dec 22, 2017, at 10:20 AM, Olivier R. wrote:
>>
>> Le 22/12/2017 à 16:10, Warren Young a écrit :
>>> 1. Your repo is public-facing. Is this a reasonable number of
>>> clients to be
On 12/22/17, John P. Rouillard wrote:
>
> I am currently running 5
>
> nc www4.fossil-scm.org 80
>
> processes and sending no input.
Ah hah!
I think the problem is this code:
http://www4.fossil-scm.org/artifact/9694a7dc?ln=1855-1858
That connection rate throttler is code
32 matches
Mail list logo