Showing Posts For Ruhrpottpatriot.7293:
Not going for an EVE-style permission system.
Me is sad
Well I guess you have your reasons for doing so. Maybe we will get something down the road.
Still I like the migration to API keys, this makes developing non-web applications so much easier.
And to all the “API-Key-Hater” (for a lack of better wording), you really should look how EVE and CCP do it. It is an awesome system and they have ran with it for years and never had any big problems.
That’s exactly why I wrote my Perl module,
Well that’s something different. If I’d code in C# and there are only c++ wrapper around I’d write something for myself. That’s not reinventing the wheel.
On the other hand if there are already five c# implementations out there I’d probably grab one of those, since it’s far less time consuming.
@Steckums: GW2.Net also has an WvW implementation (and I might add a more complete one
)
yeah well one millisecond are 10000 ticks so half a millisecond is still fast enough. Even if Anet introduces so much flags that it goes up another 5000 ticks, no one should complain about the speed. We are not in real life business applications where every ms counts or you loose half a million Dollar
In my eyes using bitwise flags for every bit of efficiency is a little bit over engineering the code.
But If you drop me your dll and a sample unit test code I’ll gladly run it through LINQ-Pad
So, I did the following query in LINQPad, with a slightly modified data dump from this forum (all I did was to add {"items":{ to the beginning, so I could parse it more easily and I attached the modified json to this post).
//read from file to leave the api call time out string[] lineArray = File.ReadAllLines(@"C:\recipe_created_items.json"); string jsonString = string.Join("", lineArray); /Deserialize var items = JsonConvert.DeserializeObject<Dictionary<string, Dictionary<int, Item>>>(jsonString)["items"].Values; Stopwatch watch = new Stopwatch(); List<long> ticksCounter = new List<long>(); for (int i = 0; i < 1000; i++) { watch.Start(); var accountBound = items.Where(item => item.Flags.Contains(ItemFlags.AccountBound)); watch.Stop(); ticksCounter.Add(watch.ElapsedTicks); watch.Reset(); } var averageTicks = ticksCounter.Average(); Debug.WriteLine("Average time 24 items out of 6849: {1} ms({0} ticks)", averageTicks, averageTicks / TimeSpan.TicksPerMillisecond); // Result: Average time 24 items out of 6849: 0.0003 ms(3 ticks)
If I convert the query into a list I get the following result:
[qutote]
Average time 24 items out of 6849: 0.5012394 ms(5012.394 ticks)
[/quote]
I had to measure the ticks, milliseconds was too inaccurate, all I got was 0 :P
And I guess I can live with 3 ticks and even with ~5000ticks time
. The real bottleneck is not LINQ but the server, if you do a whole query you will wait about 15 to 30 munutes :P
Btw: the first call takes about 4600 ticks every query after that goes between 0 and 2 ticks.