Fabricio D Voznika

age ~47

from Kirkland, WA

Also known as:
  • Fabricio Britto Voznika
  • Fabricio B Voznika
  • Lilian Voznika
  • Sabricio Voznika
  • Fabricio A

Fabricio Voznika Phones & Addresses

  • Kirkland, WA
  • 8108 NE 149Th St, Kenmore, WA 98028
  • Federal Way, WA
  • Renton, WA
  • Bellevue, WA
  • Walnut Creek, CA
  • Long Beach, CA
  • West Lebanon, NH
  • Alameda, CA

Work

  • Company:
    Google
    Oct 1, 2012
  • Position:
    Software engineer and technician lead

Education

  • Degree:
    Master of Science, Masters
  • School / High School:
    University of Washington
    2006 to 2008
  • Specialities:
    Computer Science

Skills

Distributed Systems • Software Design • Scalability • Software Engineering • C++ • Object Oriented Design • Databases • Win32 Api • C# • Multithreading • Software Development • Windows Programming • Algorithms • Systems Programming • Windbg • Agile Methodologies • Operating Systems • Windows Internals • Scrum • Debugging • Cloud Computing • Windows Azure • File Systems • Design Patterns • .Net • Java • Visual Studio • Microsoft Azure • Hadoop • .Net Framework • Eclipse • Database Systems

Industries

Computer Software

Resumes

Fabricio Voznika Photo 1

Software Engineer And Technician Lead

view source
Location:
344 Westline Dr, Alameda, CA 94501
Industry:
Computer Software
Work:
Google
Software Engineer and Technician Lead

Microsoft Oct 2003 - Oct 2012
Principal Software Engineer Lead

Dartmouth College Nov 2002 - Sep 2003
Senior Software Engineer

Ericsson Mar 2001 - Sep 2002
Software Engineer Ii

Objective Solutions 1998 - Feb 2001
Software Engineer
Education:
University of Washington 2006 - 2008
Master of Science, Masters, Computer Science
Pontifãcia Universidade CatãLica Do Paranã / Puc - Pr 1997 - 2000
Bachelors, Bachelor of Science, Computer Science
Pontifícia Universidade Católica Do Paraná 1997 - 2000
Bachelors, Bachelor of Science, Computer Science
Skills:
Distributed Systems
Software Design
Scalability
Software Engineering
C++
Object Oriented Design
Databases
Win32 Api
C#
Multithreading
Software Development
Windows Programming
Algorithms
Systems Programming
Windbg
Agile Methodologies
Operating Systems
Windows Internals
Scrum
Debugging
Cloud Computing
Windows Azure
File Systems
Design Patterns
.Net
Java
Visual Studio
Microsoft Azure
Hadoop
.Net Framework
Eclipse
Database Systems

Us Patents

  • Partitioning Of Contended Synchronization Objects

    view source
  • US Patent:
    20100287203, Nov 11, 2010
  • Filed:
    May 7, 2009
  • Appl. No.:
    12/436805
  • Inventors:
    Fabricio Voznika - Kenmore WA, US
    Alexander Verbitski - Woodinville WA, US
    Pravin Mittal - Redmond WA, US
  • Assignee:
    Microsoft Corporation - Redmond WA
  • International Classification:
    G06F 17/30
  • US Classification:
    707781, 711118, 707609, 707640, 707661, 707652
  • Abstract:
    Methods, systems, and computer-readable media are disclosed for partitioning contended synchronization objects. A particular method determines a contention-free value of a performance metric associated with a synchronization object of a data structure. A contended value of the performance metric is measured, and the synchronization object is partitioned when the contended value of the performance metric exceeds a multiple of the contention-free value of the performance metric.
  • Partitioned Reference Counter

    view source
  • US Patent:
    20130346707, Dec 26, 2013
  • Filed:
    Jun 21, 2012
  • Appl. No.:
    13/530082
  • Inventors:
    Fabricio D. Voznika - Kenmore WA, US
    Haitao Wang - Issaquah WA, US
    Jack S. Richins - Bothell WA, US
    Jasraj Dange - Redmond WA, US
  • Assignee:
    MICROSOFT CORPORATION - Redmond WA
  • International Classification:
    G06F 12/00
  • US Classification:
    711159, 711E12001
  • Abstract:
    Resource use is recorded with a partitioned reference counter. The sum of all resource counter partitions is equivalent to the total references to a resource. When one resource counter partition reaches zero, it is possible that the resource should be destroyed. To determine if this is the case, all other partitions can be checked for a value of zero. If all the partitions are zero, the resource can be destroyed. Coarse grained partitioning and add/release on all partitions can be employed to avoid extra work associated with a local partition reaching zero. Further, destroying or deleting a resource can be accomplished in a manner that avoids a race condition.

Get Report for Fabricio D Voznika from Kirkland, WA, age ~47
Control profile