Have you ever been making a game/app in the BGE or UPBGE and then somehow the frame rate drops when camera is pointing to some specific area? This is a common mistake among newcomers, and although there are several causes for this to happen, physics objects are one of the most commonly so here are some advices to take into account so you can use the correc physic type and shape in order to avoid the excesive resource consumption while executing the game engine. 
Physics Type Order:A collision shape is the shape of an object as “seen” by the collision/physics engine.
Think of a square box and a circle:
Near the corners, objects will hit or collide with the box but not the circle even though the height and width of the objects are identical.
More complex shapes as also possible. Circles/spheres are the simplest (and fastest) but tend to poorly represent many kinds of objects. Axis-aligned bounding boxes (AABBs) are the next most common/efficient. Capsules (a cylinder with half-spheres on each end) are common for characters. The common collision algorithms all support convex hulls (a polygon/polyhedron with only convex angles), and decent physics engines are typically capable of dealing with objects which have multiple shapes (allowing for objects to incorporate shapes with concave features, even though the collision engines typically can’t handle them directly).
Source
