How? AFAIK it is about wrong number of core and threads for AMD cpus. But those tests are runining on intel cpus

On Sat, Jul 20, 2019 at 7:10 PM Andre Pany via Digitalmars-d < digitalmars-d@puremagic.com> wrote:

> On Friday, 12 July 2019 at 07:47:23 UTC, Sönke Ludwig wrote:
> > Am 12.07.2019 um 00:33 schrieb Daniel Kozak:
> >> [...]
> >
> > The issue with InterfaceProxy is definitely true, this has a considerable performance hit and the new vibe-http module will get rid of that. However, even with InterfaceProxy, the performance is still well within the same order of magnitude.
> >
> > [...]
>
> In recent dmd a bug was fixed which maybe is related to your scaling observation:
>
> https://issues.dlang.org/show_bug.cgi?id=19861
>
> Kind regards
> Andre
>

On Saturday, 20 July 2019 at 21:49:56 UTC, Daniel Kozak wrote:
> How? AFAIK it is about wrong number of core and threads for AMD cpus. But those tests are runining on intel cpus
>
> On Sat, Jul 20, 2019 at 7:10 PM Andre Pany via Digitalmars-d < digitalmars-d@puremagic.com> wrote:
>
>> On Friday, 12 July 2019 at 07:47:23 UTC, Sönke Ludwig wrote:
>> > Am 12.07.2019 um 00:33 schrieb Daniel Kozak:
>> >> [...]
>> >
>> > The issue with InterfaceProxy is definitely true, this has a considerable performance hit and the new vibe-http module will get rid of that. However, even with InterfaceProxy, the performance is still well within the same order of magnitude.
>> >
>> > [...]
>>
>> In recent dmd a bug was fixed which maybe is related to your scaling observation:
>>
>> https://issues.dlang.org/show_bug.cgi?id=19861
>>
>> Kind regards
>> Andre

I wasn't aware of this detail. You are right, it doesn't solve the issue.

Kind regards
Andre