The Advertised Bandwidth is is significantly lower on TorRelay02HORUS too. Let me quote teor from another recent thread, I think the same info is helpful here:
-- begin quote --
Your relay reports a bandwidth based on the amount of traffic it has sustained in any 10 second period over the past day. You can also set a maximum advertised bandwidth on your relay. (Don't do this if you're trying to pick up more traffic.) Five bandwidth authorities measure each relay each week, and report how fast it is. Each of these factors can restrict the amount of bandwidth that the network assigns to your relay.
Here's one way of testing what your relay is capable of:
Run a Tor client as close to your relay as possible: tor DataDirectory /tmp/tor.$$ SOCKSPort [IPv4:]10000 EntryNodes your-relay-name
Then download a large file using port 10000 as a socks proxy.
That will give you some idea of how much traffic your relay can sustain, but it's worth noting that each client is limited to about 1 Mbps (I think - I can't find the manual page entry).
-- end quote --
From a quick glance, it seems that TorRelay02HORUS just isn't
providing the same bandwidth as TorRelay01HORUS. There could be many reasons for this, including hardware, other nodes on the same network rack at your host, upstream bandwidth for the datacenter, peering between the node and the bandwidth authorities, etc.
None of this is unusual. As I have said many times, when spinning up new relays, I often find it helpful to bring up many at the same time (ideally using automation like Ansible), find which ones perform best, keep those and tear down the others.