1300 placemarks take 300 second to create

[GoogleCodeExporter]

What steps will reproduce the problem?
1. use IE 
2. random create 1300 placemarks

What is the expected output or behavior? What do you see instead?
IE takes more than  5 minutes to finish the create job 

Which plugin version are you using?
my web page use google.load("earth", "1");

Which browsers and operating systems are affected?
IE & Windows XP

Please provide any additional information (code snippets/links) below.

Original issue reported on code.google.com by win3...@gmail.com on 6 Dec 2008 at 12:21

[GoogleCodeExporter]

Hi, you may want to generate one large KML string with the placemarks and then 
use
parseKml() to generate the placemark objects. Also, is there a reason you're
generating 1300 placemarks all at once?

Original comment by api.roman.public@gmail.com on 8 Dec 2008 at 6:33

[GoogleCodeExporter]

We may try to improve performance over time but there are fundamental issues 
with
JavaScript performance with large datasets. Since there are a number of 
workarounds
(regionation, parseKml(), etc.), marking this as WontFix

Original comment by api.roman.public@gmail.com on 8 Dec 2008 at 11:04

• Changed state: WontFix

[GoogleCodeExporter]

yes , not just 1300 , originally , i would like to add 6,000 placemark , but 
i've
found the problem at 1300. 

yes , i'm using javascript to generate the placemark i need 

in your reply , you said "a number of workarounds (regionation, parseKml(), 
etc.)" ,
is it true ? if yes , i can change my code to parseKml() , it would be very 
nice if
you can give me some website for reference. 

sorry , i never heard "regionation" before.

thanks x 10 

Original comment by win3...@gmail.com on 9 Dec 2008 at 1:49

[GoogleCodeExporter]

Hi win3721,

Here are a few links:

http://code.google.com/apis/kml/documentation/regions.html
http://code.google.com/apis/earth/documentation/demogallery.html?searchquery=&to
pic=kml
(see the KML parsing demos)

If you have more questions, let's continue the conversation in the Group (to 
keep the
issue tracker concise).

- Roman

Original comment by api.roman.public@gmail.com on 9 Dec 2008 at 9:57