The future of WiMAX should be assured. After all, Intel has poured billions into WiMAX, from chipsets to investments in service providers. But the question, of course, is why. Intel is a chip company, and is always looking for high-volume opportunities to sell vast numbers of chips. Shouldn't, therefore, Intel remain relatively agnostic when it comes to next-generation developments? Perhaps Intel originally thought that WiMAX would achieve critical mass well in advance of LTE, and thus LTE would be no more than a runner up. That's clearly not the case, and there's evidence now that Intel realizes this. Intel CEO Paul Otellini has said that WiMAX is spurring the development of LTE, and that's a good thing. Sean Moloney, who spearheaded WiMAX development at Intel, says he'd like to see the harmonization of WiMAX and LTE. That won't happen anytime soon, but why would he make such a suggestion? Scott Richardson, Chief Strategy Officer for Clearwire, made a similar suggestion today, by the way, during a WiMAX Webcast announcing an intellectual-property consortium.
Monday, June 16, 2008
wat is intel thinking?
Intel will shortly announce its long-awaited "Montevina" Centrino chipset that includes WiMAX functionality. While this is an obvious direction for Intel to go, I'm left scratching my head a little over this one. I have never advocated buying a notebook with a built-in WWAN adapter; that's just too much of a lock-in to a network that might not be the right choice everywhere - and you get to pay for it with hefty monthly charges whether it works for you or not. In the case of WiMAX, which will have only limited commercial availability this year, such a lock-in would be counterproductive for those who travel beyond an area with service availability. Ultimately, it will be critical mass that determines the success of 4G technologies - enough availability in enough places to convince potential customers to make the investment and commitment.
Posted by paul at 9:26 AM 0 comments
Sunday, June 15, 2008
INTRODUCTION OF INTEL
Intel Corporation (“Intel”) is a leading technological manufacturer
that largely can be credited with many of today’s technological advances,
innovations and developments – it hardly can be accused of seeking to curb
the growth of the Internet or computer technology. Indeed, these
developments have greatly enhanced the American economy, as well as
provided Americans with increased access to information. The
memberships of the Labor Policy Association, Inc. (“LPA”), the United
States Chamber of Commerce (the “Chamber”) and the California Chamber
of Commerce (the “Cal Chamber”) (collectively, “Business Amici”) are
comprised of businesses, organizations and employers that benefit from
these advancements and rely upon them to remain competitive in the global
economy. Appellant, Kourosh Kenneth Hamidi (“Hamidi”), and other
Amici1 have acknowledged the importance of email to American industry
and society in their various letters and briefs.
Simultaneously, however, American businesses, organizations and
employers have a vested interest in protecting the billions of dollars of
technological properties they purchase and maintain, and for which they
ultimately may be liable in the event of abuse.
Although Hamidi and Defendant Amici gloomily
Posted by paul at 9:11 AM 1 comments
INTEL ABSTRACT
The Intel® Core™ Duo processor is a new member of the Intel® mobile processor product line. It is the first Intel® mobile microarchitecture that uses CMP (Core Multi-Processor; i.e., multi cores on die) technology. Targeted to the market of general-purpose mobile systems, the Intel Core Duo core was built to achieve high performance, while consuming low power and fitting into different thermal envelopes.
In order to achieve the required performance, a CMP-based microarchitecture was designed to achieve power-efficient architecture, each performance improvement was evaluated against the power cost, and only the power-efficient performance features were implemented.
On top of that, special hardware mechanisms were added to better control the static and the dynamic power consumption. As a result, the Intel Core Duo processor provides higher performance in the same form factors without needing to increase the cooling capability.
Posted by paul at 9:08 AM 0 comments
Wednesday, June 11, 2008
INTEL AND AMD
The argument over an AMD CPU versus an Intel CPU and which has a higher functionality is currently raging. Simply two years ago this was not even a question. Anyone would tell you that the Intel CPU won the speed and complex algorithm war with AMD CPU's without question. Fast-forward to today and Intel is now playing catch-up to the latest in AMD technologies.
Intel played marketing games with their CPU's pricing them high and touting the functionality that they posses as cutting edge. AMD started out as the cheap alternative CPU manufacturer for computer brands such as e-Machines and low-end Compaqs. From the beginning, AMD CPU's were fighting an uphill battle to catch up with the technology in the Intel CPU. As the years have progressed, AMD has progressed.
Posted by paul at 9:29 AM 0 comments
AMD
AMD, long the oppressed rebel force in the chip industry, managed to launch an attack on the Intel Death Star with the introduction of its 64-bit Opteron processors in 2003.
Opteron ran 64-bit applications and legacy 32-bit applications without the drag on performance noted in Intel's Itanium processors. AMD upped the ante further in 2005 with the introduction of its first dual-core Opteron processors that doubled the performance of single-core Opterons.
The first chink in Intel's armor appeared in the second quarter of that year when, as Mercury Research reported, Intel's market share slipped to 82.5 %, from 82.8 % in the year ago quarter, while AMD's inched up to 15.7 % from 15.6 %
Posted by paul at 9:28 AM 0 comments
INTEL VS AMD
Perspective’s review of the 780G+Athlon 4850e combo. There’s a lot of interesting details down there. For example the differences between hybrid SLI and hybrid Crossfire – something had to be different, innit? It also shows the difference between Intel and AMD’s power efficiency designs. Some stats thrown in for good measure too – however Intel’s upcoming G45 should upset this AMD advantage. 2008 is shaping up to be quite the Mexican stand-off
Posted by paul at 9:25 AM 0 comments
Sunday, June 8, 2008
Configuring a Simple Data Flow
Now we'll continue on with designing a package to load a dimension. In this example, we copy a subset of the columns of the Sales Territory table from our OLTP source system into a table in our data warehouse.
| 1. | Drag a Data Flow task from the Toolbox onto the surface of the Control Flow tab. |
| 2. | Double-click the new Data Flow task to open the data flow design surface. Drag an OLE DB Source from the Toolbox onto the pane and change the name to Sales Territory. |
| 3. | Drag an OLE DB Destination data flow destination from the Toolbox onto the pane and change the name to DW SalesTerritory. |
| 4. | Click Sales Territory and drag the green arrow onto DW Sales Territory. You can't configure the data destination properly until it has data flowing into it. You will notice in the Sales Territory data flow source that there is a small red circle with an X in it. This is because it is missing some information. You can hover the mouse over the X to see what the problem is. We need to tell it where to find the source data, which table it is in, and which columns we want to copy. |
| 5. | Double-click the Sales Territory OLE DB Source to open the OLE DB Source Editor. |
| 6. | Set the OLE DB Connection Manager setting to SalesTracking. |
| 7. | Set the data access mode to Table or view, and select [Sales].[Sales Territory] from the list of tables. Click Columns. |
| 8. | We only want to copy TerritoryID, Name, CountryRegionCode, and Group, so check those columns. Uncheck the others. |
| 9. | Double-click the DW Sales Territory SQL Server destination to open the OLE DB Source Editor. |
| 10. | Set the Connection Manager to DataWarehouse. |
| 11. | Select [dbo].[dimSalesTerritory] from the list of tables. |
| 12. | Click Mappings. |
| 13. | Drag and drop each input column onto the corresponding destination column. The TerritoryID input column is mapped to the business key, not to the SalesTerritoryKey. SalesTerritoryKey is an internally generated surrogate key. (The editor does try to map the columns based on the name, but none of our names match. If there are any automatic mappings, it is a good idea to review them.) |
| 14. | Click OK to save the configuration. This would be a good time to save the whole solution, too. |
Posted by paul at 5:00 AM 0 comments
Tuesday, June 3, 2008
Solution Overview
Posted by paul at 8:12 PM 0 comments
Very Large Data Warehouses
Problem Statement
Many of the business problems our customer is experiencing would benefit from the kinds of BI capabilities that you have seen in previous chapters, but there is one huge technical problem that first needs to be overcomethe volume of data in a utility company's data warehouse can be staggering. The client has reduced the volume of data by loading filtered and summarized data into relational data mart databases for specific business applications. The business still finds itself constrained in many ways:
-
The summarized level of information leads to limitations in the kinds of queries that can be answered meaningfully, because some of the dimension attributes are no longer available. For example, data summarized to the month level cannot be used to predict daily traffic levels.
-
Data points from multiple systems are summarized and consolidated separately, leading to silos of information in the various data marts.
-
The users cannot get timely information on events such as the effect of promotions on network traffic. As the database grows in size, increasing maintenance time is reducing availability of the system.
-
Queries that span or summarize long time periods or many geographic areas are becoming too slow as the amount of data increases
Posted by paul at 8:10 PM 0 comments
Monday, June 2, 2008
Solution Overview
The solution we are going to examine builds a data warehouse designed with the ability to correctly represent historical information. We will use Integration Services to manage the loading and updating of slowly changing dimension tables and Analysis Services to analyze the facts in the context of the time it was captured.
Business Requirements
The high-level requirements to support the business objectives are as follows:
-
Ability to track client history. Some changes to a client's information are interesting and useful for analysis, other changes are not. Credit rating is interesting in analysis, phone number changes are not. The credit union needs the ability to know the state of their clients at any point in time, so that any analysis carried out in the client's context applies at that point in time. Any significant changes in a client's state should not overwrite existing values but should be added to the client's history. This means, for example, that when a client's credit rating changes, the periods of time when the old ratings are in effect and when the new rating is in effect are treated independently. Conversely, if the client's phone number changes, it makes no difference to any analysis, and there is no need to track old phone numbers.
-
Multidimensional transaction analysis. The solution must allow the users to analyze the transactions using the dimension values from the CRM system that were in effect at the time of the transaction, as well as by other dimensions such as the type of transaction (withdrawal, payroll deposit, and so on) and channel (ATM, Branch, Internet Banking, and so forth).
Posted by paul at 10:38 AM 0 comments
Business Problem
Posted by paul at 10:32 AM 0 comments







