I don't think so. If it was, juste when a cos or a sin vanish.<br>My first thought was that mapserver have to calculate more pixels in a rotated map than a normale map. But when i read the source code i found that it's the projection which rotate, not the map. So why this discimination? The same projection <br>
<br><br><div class="gmail_quote">2011/4/21 Stephen Woodbridge <span dir="ltr"><<a href="mailto:woodbri@swoodbridge.com">woodbri@swoodbridge.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5">On 4/21/2011 10:32 AM, Mohamed Saād HESSANE wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hy list,<br>
I have a question. I'm doing a benchmarking test of a rotated map, and i<br>
get the result in the attached file.<br>
My question is why it take more time to draw a map rotated at 45° than a<br>
map rotated at 90° or 183° ???<br>
Thank you !<br>
</blockquote>
<br></div></div>
I'm only guessing here but could it be that the math required to compute cos and sin is more costly in cpu cycles at those angles.<br>
<br>
Regardless, this is an interesting question and I love the graphic, nice job on that.<br>
<br>
-Steve W<br>
_______________________________________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org" target="_blank">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
</blockquote></div><br>