I think I made Excel do a little to much work today.

@ramen trying to run a vlookup over 40k records over 2 workbooks (second workbook had the lookup value sorted)

It didn’t seem to like that 🤷‍♂️

@ramen because I have several csv’s to match data across and find inconsistencies.

Excel other then that vlookup is pretty easy to work with otherwise.

Impressive, uses all cores to a 100%.

Why the fuck is ur excel doing this 🤦‍♂️

@marcdecline I can’t say I’ve seen excel behave any other way, and I have to use it regularly, large (20k+) record lookups over multi workbooks get complete cpu utilisation every time (4 cores / 8 threads)

no no, it was Excel who made the CPU do a little too much work

Why on earth do you need 32GB of memory?

@EmptyStack usually for multiple VM's constantly running, but it comes in handy when pushing excel hard to crunch large spreadsheets.

I work with Excel, too, usually ~5k records across multiple workbooks. I still think Excel is only hogging the CPU just because it can and it doesn't actually use it.

@lunorian So you think your browser would be able to handle it?

@C0D4 I tried importing a CSV with 1.6 million records the other day. Let me say that didn't go well. Ended up importing it to MongoDB and making a Python script instead

@vigidis

Dell Precision 5520 with some customisations.

@aaxa I find if I’m headed over the 500k line, excel is not the place you want to be working with that spreadsheet no matter the computer.

I get this every Monday also due to vlookup. Pain in the ass. Especially as my rig don’t have those resources.