func_physbox and func_breakable killing fps

Ok ok, first let me start off by acknowledging that you will all probably say "darn you RadiKal we have a tutorial for this sort of thing!", but I've read through a lot of tutorials on things like using hints and areaportals and when I tried to implement them, well, it didn't work out so well. The problem I have is this: There is a certain section of a map I'm making that is full of boxes comprised of func_physboxes and func_breakables. I finished that area of the map and went on to other parts but I'm noticing that every time I look in the direction of that area my fps drop. Drastically. Also, this is my first level and I've done many a noobish thing. For instance, I didn't know that the compiler would carve different leaves for intersecting brushes, so all of my walls extend into the floors and such. Not a great thing, really. Anyway these two things together are what I think is killing my fps in game. Now I was under the impression that using some well placed hints and/or area portals could reduce the number of objects that the engine renders, so that the fps would go back up, or at least only be bad in that one area with all the boxes. So getting around to the actual question.... what is the real difference between a hint and an area portal? If you stood on one side of an area portal could you not see anything on the other side? The part of my map that i'm having problems with is outside in a fairly open space in a kind of canyon. There is a tunnel and a doorway to a different, equally open outside area. I read the information about hints on the user's guide and the example they gave even related to a canyon like mine. I tried putting hint brushes across the top of the canyon, in the doorway, and in the tunnel but no improvement in performance was gained. Also, I tried using areaportals but it said during compilation that the areaportal bordered more than 2 portals or something like that... ANY help would be GREATLY appreciated.

Hint brushes and area portals and all that jazz are only tools that allow for experienced mappers to try and squeeze more out of the engine. They cannot make up for poor design decisions or magically fix serious problems. They should not be used by new mappers who have yet to fully grasp the basic fundamentals of mapmaking.

My suggestion is to redesign the area that has performance issues and to look for better visblocking. I would also suggest practicing better construction techniques.