- #EXCEL VBA ON SURFACE PRO UPGRADE#
- #EXCEL VBA ON SURFACE PRO PRO#
- #EXCEL VBA ON SURFACE PRO CODE#
- #EXCEL VBA ON SURFACE PRO PC#
#EXCEL VBA ON SURFACE PRO CODE#
Plus the first version only had about 50 lines of code and nowhere near the functionality or accuracy that it has today so it has more or less outgrown Excel over those two years. Thanks for the info! I wish I could have "spent those years gradually learning a better language" but this spreadsheet in it's most basic early form needed to be up and running within the first couple weeks of me being assigned to this new product development so putting that on pause and learning a new language was not an option. That need to get separated into various function calls and maybe even classes. I mean I don't know what's in those 2000 lines, so who can say for sure anyway? Any time I have a script that has anywhere near 500 lines, I ask myself wth I'm doing. He used it to show us some flow rates and such, graphed out. Our Differential Equations teacher for instance. My only experience with it is some professors using it. But if he's been working with VBA anyway, he should be familiar enough to switch languages without too much issue. So it's not a bad language to start with just to get introduced to basic programming constructs. Of course then they moved me straight into C (not C++, just straight up C.), which was a bit of a hard one but I somehow got an A in that, too. I literally had no programming experience going into college and I had no issues learning matlab first semester and I ended up better at it than most people. They have a whole section dedicated to working with XLS reads: Matlab can easily import Excel files, and it's in general a very easy language to pick up. You should have spent those years gradually learning a better language to do this in, not struggling along with VBA. You could also look into using your GPU for the calculations.
#EXCEL VBA ON SURFACE PRO UPGRADE#
You can upgrade your system to something like a hexa or octacore for an enormous fee, but it will at best provide a linear increase in compute times with amount of cores. Since it's likely proprietary, too, there's not much we can do to help you optimize it.
Your code is very likely suboptimal (no offense), especially considering you mentioned you have no programming knowledge. It's highly dependent on the way you structure your Macro.Īn i7 should be sufficient for pretty much any kind of code. How this all happens under the hood is a question best left to someone else, as I do not often use VBA (simply for sorting emails, and even for that it's horrendously slow.). If they make certain modifications and formula executions that get deferred to the program (excel itself) to run, then they might happen on other threads. Those VBA lines themselves are probably mostly run on the first core. That depends on whether they are actually doing anything with the VBA program.īut VBA code runs on a single thread (at least as far as I can see). For the large amount of simple, repetitive calculations, would I be better off using an AMD processor that has more physical cores and higher clock speeds? Would faster RAM make any noticeable difference?
#EXCEL VBA ON SURFACE PRO PC#
I'm wondering if I could do something to upgrade/modify my work PC to get the run times down.
#EXCEL VBA ON SURFACE PRO PRO#
For reference, my home PC with an i5-3570 does it in about 9 minutes which is on par with my i5/8GB Surface Pro 2. The work PC I built specifically for these runs has an i7-4790 and takes 5-6 minutes to complete the run.
The spreadsheet does some calculations in real-time within the cell equations but the bulk of the work is done by a 2000+ line VBA code that max's out my CPU and renders Excel useless. A large part of my design work as an engineer involves using a rather complicated Excel spreadsheet that I developed to run energy modeling scenarios.
0 kommentar(er)
