根据时区偏移量获取单个时区的高效实现方案咨询

Great question! The default TimeZone.getAvailableIDs(int offset) method does wasteful work here—it scans every available timezone, collects all matches, sorts them, and returns the full array, even though you only need one valid timezone ID. Let’s fix this with more efficient alternatives.

Problem with the Current Approach #

As you noticed, the underlying implementation iterates through every timezone ID, checks its offset, builds a full list, sorts it, and returns it. This is overkill when you just need a single matching timezone.

Solution 1: Early-Termination Loop (Real Timezone ID) #

Instead of collecting all matches, stop as soon as you find the first timezone with the correct offset. This cuts down on unnecessary iterations and skips the sorting step entirely.

Here’s the optimized code:

private TimeZone getTimeZone(int offset) {
    final TimeZone UTC_TIME_ZONE = TimeZone.getTimeZone("UTC");
    String[] allZoneIds = TimeZone.getAvailableIDs();
    
    for (String zoneId : allZoneIds) {
        TimeZone tz = TimeZone.getTimeZone(zoneId);
        if (tz.getRawOffset() == offset) {
            return tz; // Return immediately on first match
        }
    }
    
    // Fallback to UTC if no matching timezone exists
    return UTC_TIME_ZONE;
}

Bonus Optimization #

If you call this method frequently, cache the allZoneIds array as a static variable to avoid re-fetching it every time:

private static final String[] ALL_ZONE_IDS = TimeZone.getAvailableIDs();

private TimeZone getTimeZone(int offset) {
    final TimeZone UTC_TIME_ZONE = TimeZone.getTimeZone("UTC");
    
    for (String zoneId : ALL_ZONE_IDS) {
        TimeZone tz = TimeZone.getTimeZone(zoneId);
        if (tz.getRawOffset() == offset) {
            return tz;
        }
    }
    
    return UTC_TIME_ZONE;
}

Solution 2: Custom Fixed-Offset TimeZone (No Traversal Needed) #

If you don’t need a "real" timezone ID (like Asia/Baku) and just need to correctly format dates with the given offset, you can create a custom TimeZone directly. This avoids any iteration entirely—it’s the most efficient option for this use case.

private TimeZone getTimeZone(int offset) {
    return new TimeZone() {
        @Override
        public int getRawOffset() {
            return offset;
        }

        @Override
        public void setRawOffset(int newOffset) {
            // No-op: we're using a fixed offset
        }

        @Override
        public int getDSTSavings() {
            return 0; // No daylight savings support
        }

        @Override
        public boolean useDaylightTime() {
            return false;
        }

        @Override
        public boolean inDaylightTime(Date date) {
            return false;
        }

        @Override
        public String getID() {
            // Format as GMT±HH for clarity
            int hours = offset / 3600000;
            return "GMT" + (hours >= 0 ? "+" : "") + hours;
        }
    };
}

When to Use Which? #

• Use Solution 1 if you need a valid, existing timezone ID (e.g., for logging, user display, or systems that expect standard zone IDs).
• Use Solution 2 if you only need to compute/format dates with the correct offset—this is faster and avoids any dependency on the system’s timezone list.

内容的提问来源于stack exchange，提问作者Yan Khonski