Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
This issue has been moved from a ticket on Developer Community.
[severity:It's more difficult to complete my work]
This is similar to this issue:
https://developercommunity.visualstudio.com/t/ServiceHubRoslynCodeAnalysisServiceex/1359690
But
ServiceHub.RoslynCodeAnalysisService.exeis not involved (as much) and takes place specifically in a.razorfile.Please see the attached recording. Simple addition of attribute to
.razorcomponent will peg the CPU to 25% usage for 8-10 seconds, where the CPU usage will dip after some time but then spike back to over 25% before idling down to ~10% and then finally to 1-3%.Original Comments
DragonSpark on 3/12/2021, 06:49 AM:
Additional recording here. It takes 3-4 seconds – sometimes more – for a tag completion to occur on a simple
<div>tag.DragonSpark on 3/13/2021, 05:07 AM:
Another recording here where a simple
publicqualification of a[Parameter]property will oscillate for ~15 seconds, with the CPU sometimes hitting 35% utilization. I have seen this go for over 20 seconds but it seems shy when actually trying to record it.Feedback Bot on 3/14/2021, 11:02 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Feedback Bot on 3/15/2021, 06:51 PM:
Thank you for sharing your feedback! Our teams prioritize action on product issues with broad customer impact. See details at: https://docs.microsoft.com/en-us/visualstudio/ide/report-a-problem?view=vs-2019#faq. In case you need answers to common questions or need assisted support, be sure to use https://visualstudio.microsoft.com/vs/support/. We’ll keep you posted on any updates to this feedback.
DragonSpark on 4/9/2021, 08:34 AM:
It is not uncommon for my machine to be perpetually pegging between 30-50% while typing during .razor development. Please send halp.😛
DragonSpark on 4/15/2021, 00:40 AM:
Here’s another capture with😛
16.10-preview2. Note that the CPU is consistently pegged in the 25-30% range sometimes reaching as high as 40%. For reference/comparison, typing in Notepad++ never goes above .5% in its process.Mike-E on 4/15/2021, 04:59 AM:
Looks like the issue is a ton of GC calls from executing
Microsoft.AspNetCore.Razor.Language.DefaultRazorTagHelperBinderPhase.ExecuteCore(RazorCodeDocument)DragonSpark on 4/16/2021, 00:53 AM:
Greetings… according to this comment it would seem an ETL has not been provided for this issue, when I have provided several and in fact provided one with the original issue. Did you not receive them? Is this thing working? Is it on? Hello? Hello?😃
DragonSpark on 4/19/2021, 10:03 PM:
Any chance we can get an update on this ticket, please?
DragonSpark on 4/20/2021, 11:26 PM:
Any update on this issue would be greatly appreciated. Thank you for any consideration.🙏
Taylor Mullen [MSFT] on 4/21/2021, 11:27 AM:
Hey DragonSpark, we really appreciate your passion in this area! I’ve dug through your traces and found some problem areas. Stay tuned!
DragonSpark on 4/21/2021, 00:47 PM:
Great! Thank you so much Taylor Mullen [MSFT] for the update. It really means a lot. Best of luck with your endeavors out there.👍
Original Solutions
(no solutions)
The text was updated successfully, but these errors were encountered: