There are twi different reference we use to condor router. They are as follows:
I am not sure which reference you were speaking, but these them!!
A parallel switchbox router PARA-CONDOR
Watanabe, T.; Oda, T.; Onaga, K.
Circuits and Systems, 1990., IEEE International Symposium on
Volume , Issue , 1-3 May 1990 Page(s):2601 - 2604 vol.4
Digital Object Identifier 10.1109/ISCAS.1990.112541
A parallel switchbox router, called PARA-CONDOR, that runs an array of processors controlled by a host computer is proposed. Parallelization of congestion cost directedness distinguishes PARA-CONDOR from other parallel routers. The routing algorithm is based on congestion costs assigned on vertices: it finds a solution by iteration of searching paths of minimum total congestion costs between pairs of actual or virtual terminals, forming nets by assigning them one by one to each pair of terminals, and then correcting congestion costs for the resolution of bottlenecks (or conflicts) in path assignment
5.6 The Condor Job Router
The condor_ job_router
daemon allows you to specify a policy for routing vanilla universe jobs to one or more grid sites, through any of the grid protocols supported by Condor (e.g. gt2, gt4, Condor-C). The idea is to do as little scheduling in advance as possible and to only feed jobs to the sites as they consume them. Meanwhile, the jobs waiting to be routed are ordinary vanilla universe jobs, so they may run in the local Condor pool or in other pools via flocking. Except for having your excess jobs queue up in the vanilla universe job queue, you can get a similar effect by submitting all of your jobs as grid universe jobs and using Condor-G matchmaking. However, the router adds some additional convenience features: tracking of aggregate job states for use in routing policy, MaxIdleJobs, and blackhole throttling.
The condor_ job_router
daemon is most appropriate for high throughput work flows, where you have many more jobs than computers and you just want to keep as many of the computers busy as possible. It is less suitable for a situation where you have a small number of jobs and you need a scheduler to choose the best place to run the jobs in order to finish them as quickly as possible. The JobRouter doesn't know which site will run your jobs faster, but it can decide whether to send more jobs to a site based on whether jobs already submitted to that site are sitting idle or not and whether you have experienced a lot of recent job failures at that site.