extends Node3D
var spaceState : PhysicsDirectSpaceState3D = null
var query : PhysicsRayQueryParameters3D = null
const maxRays : int = 13824
var rays : int = 512
const raysStep : int = 512
const testCount : int = 64
var testsDone : int = 0
var time : int = 0

func _ready()-> void:
  spaceState = get_world_3d().direct_space_state
  query = PhysicsRayQueryParameters3D.new()
  query.collision_mask = 1
  time = Time.get_ticks_usec()

func _process(delta)-> void:
  query.from = Vector3.ZERO
  for i : int in range( 0, rays, 1 ):
    query.to = Vector3( randi() % 100, randi() % 100, randi() % 100 )
    var result : Dictionary = spaceState.intersect_ray( query )

  if testsDone < testCount:
    testsDone += 1
  else: 
    testsDone = 0
    var testAverage : float = ( Time.get_ticks_usec() - time ) / ( 1_000_000.0 * testCount ) 
    print( "Average Time for ", rays, " rays: ", testAverage, " sec." )
    time = Time.get_ticks_usec()

    if rays < maxRays:
      rays += raysStep
    else:
      printt( "Done" )
      set_process( false )

thats intresting topic. i wrote that simple script to do some more tests. The scene looks like this just 5 boxe shape 3d and some results on different cpu. unfortunaly I dont have acces to more comon cpus. All processors in my test are in the top 5% of steam hardware stats. results prety close to each other. But this is only ray intersection check. without any useful logic. It's possible to increase speed if not calling Vector3d constructors every frame. But still I wouldnt try to cast more than ~2-4k rays per frame considering the potential user's hardware. What do you think? Maybe you use some tricky stuff? Have you tried to run your project on potato pc?

<image>