lol well I know it probably not the right way of doing this but im making a x86-64 disassembler to c++/other languages and first it has alot of instruction codes then it will need to convert to a byte code then im shooting for c++ and javascript output c++ will be one thing but javascript is a completely different story.
I will do like swiftcoder mentioned and break it into different classes but just wanted to know what would happen with alot of functions in one class even say the disassembler to bytecode class will need a big switch and I was wanting to handle them in different functions so they can be over ridden and easily find able in a ide. I dont expect this to go anywhere just having my hand at learning more deeply about how everyting on the cpu gets done.
Considering all this, you may want to constantly reference a profiler for any future changes you make. Identify bottlenecks, evaluate if your code is too complex and figure out where you can make the code easier to read vs where you have to apply performance magic.
If you have to really go all out on a function to make it faster, you can put the old easy-to-understand version of the function in a comment, as sort of pseudo-code and go from there.
Some search words and references:
http://en.wikipedia.org/wiki/Branch_misprediction
http://www.ece.unm.edu/~jimp/611/slides/chap5_3.html
http://bigocheatsheet.com/
https://isocpp.org/wiki/faq/inline-functions
Ask if you need more specific help, eg with a function that is using too much time.