Well explained, Armin. Short version: it's not the features, but the vertices.
A significant factor there is the parsing of the vertices: GML/XML is significantly more "expensive" than JSON. If you're able to control the format of the data you're loading, try making a JSON representation of the data and including fewer attributes; this means less processing time figuring out the data, which may help raise your ceiling.
If you have control over the dataset you're trying to render, you can try a "simplify" on the data (this isn't an OpenLayers thing, it means fudging your data server-side). This removes vertices and accuracy, in exchange for raising the ceiling further. This can get dicey, though: it would be wholly unsuitable for surveying applications, but may work fine for indicating general areas such as state boundaries at large scales.
-- Greg Allensworth, Web GIS Developer BS A+ Network+ Security+ Linux+ Server+ GreenInfo Network - Information and Mapping in the Public Interest 564 Market Street, Suite 510 San Francisco CA 94104 PH: 415-979-0343 x302 FX: 415-979-0371 email: [email protected] Web: www.GreenInfo.org www.MapsPortal.org Subscribe to MapLines, our e-newsletter, at www.GreenInfo.org _______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
