原生的Android地图VS的WebView地图的业绩比较基准，哪些参数可以包含在基准 [英] Performance benchmark of native android map vs webview map, what parameters can be included in the benchmark
问题描述
我想比较本地谷歌地图（V2）与封装在Android网页视图中嵌入HTML版本。虽然这是pretty明显的是，本机地图是顺利和迅速，我必须以某种方式证明这一点。我一直在寻找在互联网上很长一段时间，似乎没有找到任何现有的基准。有谁知道谁究竟做了类似的事情？我已经在想创造我自己的这种基准的，但如何能在实际的表现来衡量？我的想法至今都：
I am trying to compare native google maps (v2) vs the embeddable HTML version encapsulated in a webview on android. While it's pretty evident that the native maps are smoother and faster, I must prove that somehow. I have been searching on the internet for quite some time and did not seem to find any existing benchmarks. Does anybody know someone who actually done something similar? I am already thinking of creating such benchmark of my own, but how can the performance actually be measured? My ideas so far are:
- 不同数量的标记，折线的措施渲染等...
- 测量地图图块加载（也许根本不可能）
- 拖动地图时，不知怎的，测量滞后。这必须以某种方式基于地图的事件，但本机为GoogleMap类似乎并不具备像onDragListener。
如果您有任何意见或知道一些现有的资源，请帮帮我！
If you have any ideas or know some existing resource, please help me!
----------------- EDITED 2014年3月1日----------------
我已经开始创建我的基准，但现在我有一些奇怪的问题挣扎 - 看到<一个href=\"http://stackoverflow.com/questions/20482647/measure-complete-time-of-adding-showing-an-array-of-markers-to-google-maps-v3\">this问题的更多详细信息。
I already started creating my benchmark but now I am struggling with some strange issues - see this question for more details.
我的基准测试的第一个版本的源$ C $ C可以发现 rel=\"nofollow\">。目前，它不包括自动测试。不过与添加不同数量的标记和线条的实验时，你可以得到的慢HTML地图是如何的想法。我还上传了一个简单的演示在YouTube上，以查看它点击这里
The source code of the first version of my benchmark can be found here. It currently does not include automated testing. Nevertheless when experimenting with adding different number of markers and lines you can get an idea of how slower html maps are. I have also uploaded a simple demo on youtube, to view it click here
推荐答案
所以你的主题pretty有趣，但要记住，如果你是在移动网络VS去为谷歌地图，还有手机V2和JavaScript V3。 JavaScript的谷歌地图还增加了一些功能，手机不提供，你可以参考的文档来了解一下。你可以在不同的参数，如执行。
1.时间花费加载（显示器）的屏幕上的地图。
2.正如你所说呈现在地图上。
3.低带宽的性能问题。
4. UI和UX。
5.可靠性
6.用户满意度
7.执行（完全题外话，但因为你正在做的论文，我会建议）
8.特点
9.在最后的定价。 （我想高达每天20000电话是免费的API密钥JavaScript的V3）
So Your topic is pretty interesting, but remember if you are going for google maps on mobile vs web, there is mobile v2 and javascript v3. Javascript google maps has some added functionalities that mobile does not offer, you can refer the docs to find out. AND You can perform on various parameters like.
1. Time it takes to load (display) the map on the screen.
2. As you mentioned rendering on the map.
3. Performance issues on low bandwidth.
4. UI and UX.
5. Reliability
6. User Satisfaction
7. Implementation (Complete off topic but since you are doing a thesis I will recommend that)
8. Features
9. At last pricing. (I think upto 20000 calls per day is free on one API key on javascript v3)
注意
任何人随意编辑和添加一些参数标杆。
NOTE
Anyone feel free to edit and add some more parameters for benchmarking.
这篇关于原生的Android地图VS的WebView地图的业绩比较基准，哪些参数可以包含在基准的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
