3 ms·
Do I just have a really fast computer (I’m using a MacBook Pro)? I’ve never experienced this indexing issue.
by irrational 4y ago
Do I just have a really fast computer (I’m using a MacBook Pro)? I’ve never experienced this indexing issue.
- alias_neo 4y agoWhile not quite 10 minutes, I'm on a 12 core i7 Dell XPS, I have to switch between half a dozen or so Go projects in a day sometimes and it really can take a couple of minutes each; long enough to be annoying, not long enough to grab a coffee. Edit: I should say 12-thread, not 12-core, just to be clear on the performance level we're expecting here. It's a 6c/12t i7.
- Sakos 4y agoI'm on a MacBook Pro with M1. Indexing is a pain in the ass for me.
- lars_francke 4y agoMaybe. I used to be on MacBook Pros back in the days when I was working on Java and indexing was the bane of my existence. I usually worked with 3-10 big Java projects in parallel (e.g. HBase, Hadoop, Hive, NiFi, Kafka) and indexing could (not exaggerating) take up to 4 hours in total. NiFi is one of the worst offenders. And switching branches means it starts all over again. I haven't worked with Java in ~2 years so I'm not sure how bad it is now. I might start a NiFi index job just for fun...