Uli, Robert,
I finally settled on using the rate limiter package to achieve what I need.
I have a machine with 40 vCPUs and when I use a rate limiter with a rate
limit of 1000, I am able to generate HTTP requests at that rate. (There are
other processes running on this RHEL 7 machine, but it is
I think the OPs question was specifically about the cost of returning from a
function - it is the same.
> On Feb 3, 2022, at 8:03 PM, Connor Kuehl wrote:
>
> On Thu, Feb 3, 2022 at 7:07 PM Paulo Júnior wrote:
>>
>> Hi all.
>>
>> I hope you are well.
>>
>> Is there a big difference, in ter
On Thu, Feb 3, 2022 at 7:07 PM Paulo Júnior wrote:
>
> Hi all.
>
> I hope you are well.
>
> Is there a big difference, in terms of performance or functionality, between
> declaring []*Person or []Person as a return type of a function?
If you find yourself iterating over a group of structs like t
+1. Sometimes the compiler optimizations are even worse if they change the
behavior the chip was typically expecting.
> On Feb 3, 2022, at 2:23 PM, Ian Lance Taylor wrote:
>
> On Thu, Feb 3, 2022 at 7:21 AM Didier Spezia wrote:
>>
>> It seems Aarch64 benefits more from the register-based AB
No. Because a slice is a slice. But there are several performance differences
in the usage.
> On Feb 3, 2022, at 7:09 PM, Paulo Júnior wrote:
>
> Hi all.
>
> I hope you are well.
>
> Is there a big difference, in terms of performance or functionality, between
> declaring []*Person or []Pe
It depends on what you do with it, and how you use it.
[]*Person is a slice of pointers, they're small.
[]Person is a slice of structs, they're bigger than pointers.
The first requires a level of indirection to access, the second doesn't.
The first requires no copying of structs when you're itera
On Thu, 2022-02-03 at 14:26 -0800, Kamil Ziemian wrote:
> Hello,
>
> I was handed proof-of-concept app written in Python. It seems
> underdeveloped, buggy and running it first time is a pain, because of
> dependencies. Basically it need to read some graphs stored in JSON
> files and manipulated the
Hi all.
I hope you are well.
Is there a big difference, in terms of performance or functionality,
between declaring *[]*Person* or *[]Person* as a return type of a function?
Code sample https://go.dev/play/p/tBAod1hZvYu
Thank you and best regards.
Paulo.
--
You received this message becaus
Hi all.
I hope you are well.
What are the main use cases for traditional web applications (I mean
non-SPA) development with Go? In other words, in a world of Single Page
Applications (SPA) and its frameworks (such as Angular, React, Vue, so on)
where does Go have space?
Best regards.
Paulo.
Hello,
I was handed proof-of-concept app written in Python. It seems
underdeveloped, buggy and running it first time is a pain, because of
dependencies. Basically it need to read some graphs stored in JSON files
and manipulated them accordingly and write them to JSON files again.
It seems that
I will try to follow development of GoAWK.
czwartek, 3 lutego 2022 o 22:38:46 UTC+1 ben...@gmail.com napisał(a):
> Recently I switched (so to speak) my GoAWK interpreter from using a
> tree-walking interpreter to a bytecode compiler with a virtual machine, and
> got a noticeable performance boo
Recently I switched (so to speak) my GoAWK interpreter from using a
tree-walking interpreter to a bytecode compiler with a virtual machine, and
got a noticeable performance boost. Write-up here if you're interested:
https://benhoyt.com/writings/goawk-compiler-vm/
TLDR: It's significantly more c
On Thu, Feb 3, 2022 at 7:21 AM Didier Spezia wrote:
>
> It seems Aarch64 benefits more from the register-based ABI than x86_64.
> I don''t see really why. Does anyone have a clue?
My view is that the x86 architecture has fewer registers and has had a
massive decades-long investment in performance
Usually Arm cpus have a lot more registers to pass values in.
> On Feb 3, 2022, at 9:21 AM, Didier Spezia wrote:
>
> We are using our own benchmark to evaluate the performance of different CPU
> models of cloud providers.
> https://github.com/AmadeusITGroup/cpubench1A
>
> One point we have r
We are using our own benchmark to evaluate the performance of different CPU
models of cloud providers.
https://github.com/AmadeusITGroup/cpubench1A
One point we have realized is the results of such benchmark can be biased
depending on the version of the Go compiler.
For instance, the register-
> From the tests that I have performed, I can see that a Ticker pretty
accurately fires at every 1ms interval.
It will depend on the load on your machine. As the load on the machine
increases, so with the jitter in the tick time.
On Thu, Feb 3, 2022 at 1:19 AM Robert Engels wrote:
> I am unclea
16 matches
Mail list logo
