Well, it primarily depends on your particular implementation and data set.
A poorly balanced tree will mean you have to search way more data than you need to. Make sure that your tree construction is sane.
It could also depend on how you find the k neighbors. If your algorithm searches the tree for the closest neighbor and stores it, then searches for the second closest and stores it etc, then you're not doing the search very efficiently. Instead keep a running list of the k nearest neighbors and bump points out of the list as you find closer ones traversing the tree. This way you search once, instead of k times.
Either way, it sounds like you're doing this for a course. Try talking to your professor, TAs, or classmates to see if your results are typical.