Re: Is this mailing list obsolete now?
Agree. GH is ok for people involved in dev. I want to see topics into my mailbox, even if they are not relevant to my use case(s). This way I learn from others' issues. Push is definitely better than pull/search in case of Couch. In any case, if GH discussions are selected, then there must be a sync to the list. And webhooks are not always reliable, the email shall be coming directly from GH, as it is in Gitlab, for example. And.. GH is now MS... :( Cheers! On 12.07.20 г. 23:07 ч., Miles Fidelman wrote: > Well, as a user, I kind of find that the move to a github discussion > is not at all helpful. Email lists are a time-proven mechanism - why > break what ain't broke. > > Miles Fidelman > > On 7/12/20 3:43 PM, Kiril Stankov wrote: >> Hi, >> >> I see that some topics on the list are not in the github discussions and >> vice versa? >> >> Shall we all consider the mailing list obsolete and move to github? >> >> Is there a way to get summaries from github or other kind of >> notifications by email? >> >> Cheers, >> >> Kiril. >
Re: Is this mailing list obsolete now?
Well, as a user, I kind of find that the move to a github discussion is not at all helpful. Email lists are a time-proven mechanism - why break what ain't broke. Miles Fidelman On 7/12/20 3:43 PM, Kiril Stankov wrote: Hi, I see that some topics on the list are not in the github discussions and vice versa? Shall we all consider the mailing list obsolete and move to github? Is there a way to get summaries from github or other kind of notifications by email? Cheers, Kiril. -- In theory, there is no difference between theory and practice. In practice, there is. Yogi Berra Theory is when you know everything but nothing works. Practice is when everything works but no one knows why. In our lab, theory and practice are combined: nothing works and no one knows why. ... unknown
Re: Is this mailing list obsolete now?
Hi Kiril, On 12/07/2020 15:43, Kiril Stankov wrote: I see that some topics on the list are not in the github discussions and vice versa? Shall we all consider the mailing list obsolete and move to github? Not at all. We're currently in early, closed beta testing of the GitHub Discussions functionality. So far, we're happy with it, but there's no telling what will happen. It's been pretty popular, though, as you can see. Is there a way to get summaries from github or other kind of notifications by email? The intent is that, once GitHub releases webhook functionality for Discussions, we'll have at least unidirectional integration of GH Discussion posts mirrored to this mailing list. They've indicated this won't happen prior to the public beta launch, and possibly not before the feature is out of beta. It's unclear yet whether we'll be able to enable posting to GH Discussions back from replies on the mailing list, but it's something under review and has been requested from GitHub development and ASF Infra. -Joan "tempus fugit" Touzet
Is this mailing list obsolete now?
Hi, I see that some topics on the list are not in the github discussions and vice versa? Shall we all consider the mailing list obsolete and move to github? Is there a way to get summaries from github or other kind of notifications by email? Cheers, Kiril.
Re: Fastest way to get a doc _rev
Heya Garren,
great point, I’ve adjusted things to measure from last row sent in the request
to the end of the response[1], and update the results (not much of a difference
overall), numbers go up a little, but the doc size seems to make little
difference.
Note that this is a rather speed SSD system here (recent Mac mini) and fast
CPUs.
I’m running the tests many times to avoid caching artefacts, but that means all
access should be cached. So you’d likely see more differences on slower disk and
for uncached requests.
[1]: behold the bashism: RESP=`curl -sv --trace-time
http://admin:admin@127.0.0.1:5984/benchbulk-1/_all_docs?key=\"0050\;
2>&1`; SENT_TS=$(echo "$RESP" | grep -Eo \(.\{15\}\)\ \>\ Accept | sed -e 's/
> Accept//' | sed -e 's/[:.]//g'); END_TS=$(echo "$RESP" | grep -Eo
\(.\{17\}\)\ ?\ Connection | sed -e 's/\ \*\ Connection//' | sed -e
's/[.:]//g'); echo $(($END_TS-$SENT_TS))
> On 12. Jul 2020, at 16:58, Garren Smith wrote:
>
> Hi Jan,
>
> That is a really interesting experiment. I was trying to benchmark
> _all_docs recently and I've noticed is that it will stream the results, so
> it returns the header and the start of the body before its done any actual
> work. I'm not 100% sure if that is the case when `key=` is used. You might
> have to adjust your benchmark to check for the first `{` to signify the
> start of a document.
>
> Cheers
> Garren
>
> On Sun, Jul 12, 2020 at 3:37 PM Jan Lehnardt wrote:
>
>> Hey all,
>>
>> based on a question in our new GitHub Discussion board, I got interested
>> in what is faster: retrieve a doc _rev with a HEAD request or with an
>> _all_docs?key=docid request. The results might be interesting for folks:
>>
>>
>> https://github.com/apache/couchdb/discussions/2996#discussioncomment-36190
>>
>> Best
>> Jan
>> —
Re: Fastest way to get a doc _rev
Hi Jan,
That is a really interesting experiment. I was trying to benchmark
_all_docs recently and I've noticed is that it will stream the results, so
it returns the header and the start of the body before its done any actual
work. I'm not 100% sure if that is the case when `key=` is used. You might
have to adjust your benchmark to check for the first `{` to signify the
start of a document.
Cheers
Garren
On Sun, Jul 12, 2020 at 3:37 PM Jan Lehnardt wrote:
> Hey all,
>
> based on a question in our new GitHub Discussion board, I got interested
> in what is faster: retrieve a doc _rev with a HEAD request or with an
> _all_docs?key=docid request. The results might be interesting for folks:
>
>
> https://github.com/apache/couchdb/discussions/2996#discussioncomment-36190
>
> Best
> Jan
> —
Fastest way to get a doc _rev
Hey all, based on a question in our new GitHub Discussion board, I got interested in what is faster: retrieve a doc _rev with a HEAD request or with an _all_docs?key=docid request. The results might be interesting for folks: https://github.com/apache/couchdb/discussions/2996#discussioncomment-36190 Best Jan —
