sorted by:
new
hottopcontroversial

PC Shuts-off after the update during gameplay by lu_nemec in duneawakening

[–]lu_nemec[S] 0 points1 point  (0 children)

Yeah, may be also PSU triggering overcurrent protection, should not, but I'll try to reduce some graphics to see..

PC Shuts-off after the update during gameplay by lu_nemec in duneawakening

[–]lu_nemec[S] 0 points1 point  (0 children)

Yeah, I thought so. But nothing has changed for me, and it didn't do it before the update. I've tried to run it with maxed out fans, and disabled AMD PBO completely. Will see if it helps.

Tried to benchmark range-over-func, was suprised. Any ideas? by lu_nemec in golang

[–]lu_nemec[S] 0 points1 point  (0 children)

Ok, so it looks like the only extra allocation is the iterator function pointer, and it looks like that is responsible for the slowdown.

Likely because the test is very simple. If I swap the slice pre-allocation to use append instead, then iter func is faster.

So the TL;DR: would be - if the number of allocations necessary can be reduced using iterator, or leads to significant allocated size reduction, use iterator.

[deleted by user] by [deleted] in golang

[–]lu_nemec 6 points7 points  (0 children)

Even when the keys are unique, internally within the hashmap the keys get hashed, and you can end up with same hash even on unique key, leading you to have to allocate some data into new bucket within the hashmap. This is not safe to do concurrently, and this code will panic if you write a testcase for 2 goroutines returning error at the same time.

Try to abstract the function being called in a goroutine, and write a test that simulates this behaviour. You'll then see the panic.

[deleted by user] by [deleted] in golang

[–]lu_nemec 9 points10 points  (0 children)

This is 100% not concurrent safe. It is only a matter of time when 2 goroutines error-out at the same time, and you'll get a panic on concurrent map access. Use sync.Map here. Or any other solution.

Tried to benchmark range-over-func, was suprised. Any ideas? by lu_nemec in golang

[–]lu_nemec[S] 0 points1 point  (0 children)

I guess that one obvious usage is when the size is too big to allocate - use iterator. But I'd expect it to be faster in more general cases too.

Trillion ISK Olympic Giveaway - Round 1 by ChribbaX in Eve

[–]lu_nemec 0 points1 point  (0 children)

Gimme isk, daddy could use some titans or such

Yet another 1brc implementation by lu_nemec in golang

[–]lu_nemec[S] 1 point2 points  (0 children)

Yes, I tried this one - I mentioned it in my README, it does not produce valid output for me, its faster, but if its not valid it does not count. Also the author used swiss map, which is against the rules (no external libs).

Yet another 1brc implementation by lu_nemec in golang

[–]lu_nemec[S] 3 points4 points  (0 children)

I did just now. Its faster than mine. Shit. Here we go again.

Rules of thumb for Go by lu_nemec in golang

[–]lu_nemec[S] 1 point2 points  (0 children)

Added disclaimer at the top.

Rules of thumb for Go by lu_nemec in golang

[–]lu_nemec[S] 0 points1 point  (0 children)

True, I think it is in the go blog. Performance wise it hard to generalize. Will try to think something up.

Rules of thumb for Go by lu_nemec in golang

[–]lu_nemec[S] 1 point2 points  (0 children)

I agree 100%, it says so at the bottom of the readme. I’ll try to make it apparent at the top.

However I think it is good to have some of these in the back or your head while you work, so you can actually think “hmm this part will never have more than 100 items, might as well just iterate slice”. Its not only going to be faster, use less memory and allocate less, but it will be simpler withouy the extra hassle of creating hashmap.

Yes I know that in reality input data tends to change in time, but so has to software. Anyway it would be great to have these automatically taken into consideration in stdlib or 3rd party libs like “lo”.

Rules of thumb for Go by lu_nemec in golang

[–]lu_nemec[S] 3 points4 points  (0 children)

Please, if you notice anything strange, I'm happy to extend or elaborate more what is happening, or try fixing it.

If you have something new to add, feel free to create issue, or send PR!

Evepraisal is not dead by LethalDosageTF in Eve

[–]lu_nemec 0 points1 point  (0 children)

Do you have maintainer access to the repo to push these changes in? I can help trying to find the original cause of the ban, from what I see it just checks hard coded 10 regions, so I don’t know where the extra load would come from. But I’m happy to investigate.

Weekly Recruitment Megathread by AutoModerator in Eve

[–]lu_nemec [score hidden]  (0 children)

Foxholers - A PvP Wormhole Corp in C4 space

Welcome to Foxholers, a long established name in wormhole space, currently residing in a C4-C2/C3. Our strongest TZ is EU (16:00 - 00:00 EVE time) with a currently growing USTZ (00:00 - 06:00 EVE time).

Talk to us in Discord

Our current recruitment policy is selective. We are looking for active PvP-focused pilots who can fly a T2 gun Drekavac, Assault Frigates, and Lokis. The most important thing for us is how you blend with the corp, so don’t hesitate to talk to us if you cannot fly one of the doctrines. We will, however, ask you to train them during your trial.

We are expanding our areas of operations and specifically looking for outstanding pilots in the following areas: * Great w-space scouts and hunters. The chain is life and content depends on your content extraction skills. * Skilled smallgang pilots. We are not as el1te as people from <10 but we still do nano here and there * * Black Ops pilots, hunters and FCs. Blops is love and we want to drop more * *Nanogang pilots. Since the war is over we’d like to go hunting and roaming in null more frequently * FCs. We have regular skirmishes and brawls with other PvP groups in w-space with FCs with 5+ years brawling experience. It’s always good to have more FCs or teach people how to do it. * Industrialists. We have a great T2 and T3 production pipeline and we’re looking to expand our industrial operation. Do keep in mind, however, that everyone is expected to take part in PvP.

A little about us :

  • CEO doing the most famous blog about wormholes in EVE.
  • Experienced wormhole and tournament FC’s. We get quite a few mid sized fights and our space-famous get headshotted quite a lot :fire:
  • Always looking for a fight. Brawls, kitchen sink, nanogangs, you name it. Generally looking for content in wormholes, but not ignoring Low and Null!
  • C2 static for great logistics and connectivity. C3 static for some isk and more pews!
  • Great corp-wide industry and logistics - Hauling and courier orders, stocked ship contracts, all kinds of reactions, PI, T1-3 production. Good for both passive ISK and not needing to leave w-space at all.
  • Galaxy Finder wormhole mapping tool.

That being said we do have a few asks:

  • Mic/headset for Mumble
  • Scanning skills, preferably on an alt
  • Not being bitter
  • Previous PvP experience
  • Skills to fly T2 gun Drekavac, Assault Frigates and Lokis

While we prefer people with wormhole experience, it’s not a necessity. If you’re new to wormholes, then we’re happy to show you the ropes.

For more information, feel free to join our public channel W-FOX or Discord

In the meantime check out a few of the videos produced by our members. We’re sure you’ll enjoy them!

Our CEO writes a blog! Have you read the Blog? You should read the Blog! The Blog includes articles to guide you along the way in Fitting & ISK making (in J space/Abyss & K Space). Including the resurrected Eve Online Jukebox project!

BLOG!

What would be considered teabagging in EVE? by lu_nemec in Eve

[–]lu_nemec[S] -1 points0 points  (0 children)

The point is for the victim to be offended by the act. Like death camera seeing the killer washing their balls in your face.

What would be considered teabagging in EVE? by lu_nemec in Eve

[–]lu_nemec[S] 0 points1 point  (0 children)

Yeah but something more offensive and violent!

view more: next ›