Monoprice Titan Series Tilt TV Wall Mount Bracket - for TVs 32in to 46in Max Weight 125lbs Extension Range of 3.2in to 24.0in VESA Patterns Up to 400x400 Black

One of the great things about the new HDTVs is that they can be easily mounted to a wall, which frees the top of your furniture from a big heavy television and provides theater-like viewing angles, all in the comfort of your own home.When purchasing a wall mount there are several basic considerations. The first is the weight of your display versus the weight limit of the mount. You should look for a mount with a weight capacity that exceeds the weight of your TV by at least 50%. The reason for this is that the rated weight capacity of a mount is the absolute maximum weight it can withstand without incurring a structural failure of some kind. Also, the weight of the mount itself is included in the maximum capacity. The second thing to look for is a mount that can accommodate the mounting holes on the back of your TV. The actual size of the display itself (e.g., 42") is of almost no concern. The owner's manual of your TV should show the VESA size required, which is measured in millimeters. The third thing to look for is the type of mount. In general, there are three basic types: fixed, tilting, and fully articulating with tilt, swivel, and extension. Which you should choose depends entirely on your needs and your budget. This mount has the following features: Mount Type: Fully articulating Wall Type: any Minimum VESA: 75x75Maximum VESA: 400x400Weight Capacity: 125 lbsTypical Display Size: 32~46"Minimum Extension: 3.2"Maximum Extension: 24"Tilt Range: +5° to -15°Swivel Range: -90° to +90°Material: Steel Wall Plate Dimensions: 3" x 12.5"Front Plate Dimensions: 18.6" x 17.3"Features: fits VESA 75x75/100x100/200x100/200x200/400x200/400x400, cable management, hardware included

ASIN

B005E2YEPQ

Embedding

CLIP ViT-L/14 · 768d

Distance metric

cosine

Doc fetch

2ms·cache hitGET /v2/namespaces/amazon-products/documents/B005E2YEPQ

How it works

Similar query

24msnearest_to_id → /query

Doc fetch goes through Layer's Aerospike pull-through cache; cache hit served the row without touching turbopuffer. The similar query asks Layer for nearest neighbors of the stored product vector — queries don't go through the doc cache, so no cache header is set.