📝 doc: failed optimization
							parent
							
								
									6db6dc3725
								
							
						
					
					
						commit
						b2e8c878d1
					
				
							
								
								
									
										6
									
								
								notes.md
								
								
								
								
							
							
						
						
									
										6
									
								
								notes.md
								
								
								
								
							|  | @ -64,6 +64,12 @@ Result: Regressed from 3200 to 3600. Not sure why. | |||
| 
 | ||||
| Plan: OP_GETFIELD hits the constants a lot. I thought caching it and not dereferencing the chunk and block constantly might help. | ||||
| 
 | ||||
| ## Splitting up the opcode match | ||||
| 
 | ||||
| Result: No change, 3200 to 3200. Maybe Rust was already optimizing this into an optimal jump table? | ||||
| 
 | ||||
| Plan: Maybe if the hot inner opcodes, OP_GETFIELD, OP_MUL, and OP_SETFIELD get their own match statement at the top of the function, the step function can exit sooner. | ||||
| 
 | ||||
| ## Iterating over instruction list | ||||
| 
 | ||||
| (upcoming) | ||||
|  |  | |||
		Loading…
	
		Reference in New Issue
	
	 _
						_